[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] Problem with diversion

From: Werner LEMBERG
Subject: Re: [Groff] Problem with diversion
Date: Sun, 27 Apr 2003 10:48:22 +0200 (CEST)

> [...] I'd figured out a couple of the elementary things since my
> first post (enclosing the call to a diversion between .nf .fi
> requests, for instance) but most of them I would never have figured
> out on my own, either from the existing documentation or trial and
> error - especially the nifty .ss trick (I'm not sure I understand
> yet *how* this works, or how anyone would stumble upon it...).

Well, you get some deeper insight while reading the source code for
fixing bugs :-) I'll add some information about discardable whitespace
to groff.texinfo.

> Your version does exactly what I want - I will now complicate
> matters entirely by trying to get a *second* series of footnotes
> below the first...

It should be rather straightforward.  I believe this is one of the few
things which are much easier to code with groff than with TeX.

> One thought: given the caution you show is needed in using the .br
> request, perhaps this passage in groff_tmac.5 (which I was clinging
> to as a definitive statement of how to use diversions!) might be
> amended:
> "To be on the secure side, enclose everything that has to do with
> diversions into a pair of line breaks; for example, by amply using
> .br requests.  This rule should be applied to diversion definition,
> both inside and outside, and to all calls of diversions.  This is a
> bit of overkill, but it works nicely."

The very info you need is already in groff_tmac.5:

  [If you really need diversions which should ignore the current
  partial line, use environments to save the current partial line
  and/or use the .box request.]

Perhaps this should be extended slightly.  Any suggestions how to
reformulate the section on diversions in groff_tmac.5?

Anyway, groff_tmac.5 just gives a rough overview.

> By the way, do you think it would be useful to have a simple macro
> set like this in the info documentation, together with line-by-line
> commentary, just so that a beginner can see how traps, diversions
> and environments fit together - the full macro packages are probably
> too complex to be of use pedagogically.

Not in the info file but in an accompaning document like UTP.  I
haven't checked this book but it should cover everything needed.
Otherwise, we will add something appropriate.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]