Re: [Groff] horizontal trap

2016-01-01 Thread Daode
Happy new (Christian++) year everybody. Tadziu Hoffmann wrote: |> [...] and also supports five different builtin styles for |> verbatim output instead of only a silly numbered one. | |Okay, I'm curious. What different styles apart from numbering |could there possibly be? (I can't think of

Re: [Groff] horizontal trap

2016-01-01 Thread Tadziu Hoffmann
> [...] and also supports five different builtin styles for > verbatim output instead of only a silly numbered one. Okay, I'm curious. What different styles apart from numbering could there possibly be? (I can't think of any, except of course for variants of this, such as numbering only every f

Re: [Groff] horizontal trap

2016-01-01 Thread Ralph Corderoy
Hi Tadziu, > > At the bottom of the page, if the maximum is too long, flag this > > page as a problem; for example, .tm output, or add something to the > > page itself for searching. > > But if we're only interested in flagging the output pages with no > direct connection to the location of the p

Re: [Groff] horizontal trap

2015-12-31 Thread Steffen Nurpmeso
Tadziu Hoffmann wrote: |> A trap set just below the current output position could record |> the maximum .n seen on this page, moving the trap down each time. | |Indeed, trapping output instead of input would have the added |advantage that overlong lines could be detected even if the |text wa

Re: [Groff] horizontal trap

2015-12-30 Thread Tadziu Hoffmann
> A trap set just below the current output position could record > the maximum .n seen on this page, moving the trap down each time. Indeed, trapping output instead of input would have the added advantage that overlong lines could be detected even if the text was processed in fill mode. > At the

Re: [Groff] horizontal trap

2015-12-29 Thread Ralph Corderoy
Hi, > It works as expected, complaining about the 3.5i line that, together > with the 1i indent, exceeds 4i, as do the last two lines of > description. (Line 39 being the ".in".) I wonder if the OP's problem could also be tackled using the `.n' number register? The ‘\n[.n]’ register contain

Re: [Groff] horizontal trap

2015-12-29 Thread Ralph Corderoy
Hi Tadziu, > The behavior described may appear puzzling, but in > > > \Z'\l'4i''four inch > > the \Z'...' does mean "zero width" (really!) A-ha! Of course. Silly me. :-) Together with Carten's comment on indent, I end up with this. .de settrap . it 1 gotline . di prevline

Re: [Groff] horizontal trap

2015-12-28 Thread Dave
I love this list. Thank you, everyone!

Re: [Groff] horizontal trap

2015-12-28 Thread Tadziu Hoffmann
> \Z'\l'4i''four inch If you need a text line of a specified width, you can switch the rule and the label around: .de LR \Z'\\$1 inch'\D'l \\$1i 0' .. Using this .LR 1 .LR 2 .LR 3 .LR 4 .LR 5 .LR 6 will then indeed trigger the length warning for the above lines 5 & 6.

Re: [Groff] horizontal trap

2015-12-28 Thread Tadziu Hoffmann
The behavior described may appear puzzling, but in > \Z'\l'4i''four inch the \Z'...' does mean "zero width" (really!), so the total width of this line is only the width of the text "four inch" (which is less than 4 in.). > Line 32 exceeds width. > Line 33 exceeds width. This is tr

Re: [Groff] horizontal trap

2015-12-28 Thread Carsten Kunze
Hi Ralph, > The `.in 1i' gives 2i indentation. Without diversions, this doesn't > happen so in some way the token for indentation occurs once originally > and is "replayed" by .prevline? I'm sure this has been discussed > before, but my Google fu let me down. .in should be set to 0 when the di

Re: [Groff] horizontal trap

2015-12-28 Thread Ralph Corderoy
Hi Peter, > Since you're in no-fill mode, it's a perfect job for the little-used > input line trap request. This should do what you want. I had a play with this, and renamed some things to understand what was going on. .de settrap . it 1 gotline . di prevline .. . .de go

Re: [Groff] horizontal trap

2015-12-27 Thread Peter Schaffter
On Sat, Dec 26, 2015, Dave wrote: > Here's what I'm trying to do. I have a lengthy input file to be > processed in no-fill mode. For 99% of this file, that will work > just fine: that is, the input lines will fit within the the page. > A few lines, however, are too long for the page, and in no-fi

Re: [Groff] horizontal trap

2015-12-27 Thread Ralph Corderoy
Hi Dave, > I don't want groff to handle these [long] lines; the exact way each > such line should be handled depends on a number of factors and really > requires manual intervention. But I do want groff to alert me to such > cases, so that I know where to find them without having to flip > throug