Colin Watson dixit:
>would mean that line/byte numbers would be wrong, which could be
>confusing.
They are wrong anyway, as the macro packages count for byte numbers
too, at least in the iconv example. But still a point: we could just
wc the macro package first.
>mdoc; docj.tmac still has it, commented as "parse argument vector
>(recursive)". As far as I can tell this was replaced by the
>doc-parse-args macro, probably in Werner Lemberg's complete rewrite of
>mdoc in March 2001. However, it wasn't obvious to me how to upgrade your
>macro.
Interesting… why a rewrite, I wonder. But yes, parse argument vector
recursively sounds about right. Maybe I can use something like this:
│.if \n(.g \{\
│.de aV
│.doc-parse-args \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8 \\$9
│..
│.\}
I think this use of a more than two character macro will be tolerated
by AT&T nroff since it’s if’d out anyway.
The other option would be GNU groff mdoc tmac file upstream considering
to add back support for the aV macro…
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font. -- Rob Pike in "Notes on Programming in C"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
