> (It seems one list adds [Groff] and the commit list adds [groff] and so
> Mailman doesn't uniq them.)
Should be fixed now, using `[groff]' everywhere.
Werner
>> BTW, doesn't
>> http://git.savannah.gnu.org/cgit/groff.git/tree/tmac/strip.sed still
>> have a `#' comment from before Brandon's change? tmac/fixmacros.sed
>> also has one.
>
> That's true:
>
> 222812ab4 (Werner LEMBERG 2006-06-06 16:49:39 + 4) # strip comment
That probably predat
At 2017-11-08T11:37:37+, Ralph Corderoy wrote:
> Hi Werner,
>
> > What about putting this information into a tmac.sed.README or
> > something similar?
>
> I'm not sure how useful the information was? And how much it might
> mislead if it's read instead of the sed. :-)
If my explanation was
Hi Werner,
> What about putting this information into a tmac.sed.README or
> something similar?
I'm not sure how useful the information was? And how much it might
mislead if it's read instead of the sed. :-)
BTW, doesn't
http://git.savannah.gnu.org/cgit/groff.git/tree/tmac/strip.sed still
have
>> Unfortunately, this is problematic. Portable sed scripts shouldn't
>> have comments at all... Have a look into the `autoconf' manual
>> (type `i sed RET') for limitations of `sed' on various platforms –
>> maybe this is no longer of relevance today, but there are high
>> chances that groff ge
At 2017-11-07T22:21:30+0100, Werner LEMBERG wrote:
> > tmac/strip.sed: Explain operations.
> >
> > +#
> > +# 1. Strip whitespace after a leading ".".
> > ...
>
> Unfortunately, this is problematic. Portable sed scripts shouldn't
> have comments at all... Have a look into the `autoconf' manua
> tmac/strip.sed: Explain operations.
>
> +#
> +# 1. Strip whitespace after a leading ".".
> ...
Unfortunately, this is problematic. Portable sed scripts shouldn't
have comments at all... Have a look into the `autoconf' manual (type
`i sed RET') for limitations of `sed' on various platforms
