Re: [Groff] clashings with .chop

[Werner LEMBERG]

> > BTW, .chop shouldn't be used with macros.  It makes only sense for
> > diversions to strip off the final newline.  Everything else will
> > produce crap.  Read the section "`gtroff' Internals" (Node `Gtroff
> > Internals') in groff.texinfo for more information.
>
> Would it make sense and would it be difficult to move .chop from the
> "input token" level to the "output node"? (a TODO would be ok for
> the moment).

I don't think so.  Since macros, strings, and diversions are virtually
the same, .chop has to work with the general structure behind those
three concepts.  And since this structure can contain both input
tokens and output nodes intermixed, it can't be restricted to nodes
only.


    Werner