ke it or not the parser needs to be aware of this.)
--
Colin Watson (he/him) [cjwat...@debian.org]
On Sat, Nov 02, 2024 at 07:50:23PM -0500, G. Branden Robinson wrote:
> At 2024-11-02T19:06:53+0000, Colin Watson wrote:
> > How embarrassing. Could somebody please file a bug on
> > https://gitlab.com/man-db/man-db/-/issues to remind me to fix that?
>
> Done; <https://
(now with some local vim macros fixed to stop accidentally corrupting
the To: lines of some of my outgoing emails ...)
On Sat, Nov 02, 2024 at 08:09:29PM -0500, G. Branden Robinson wrote:
> At 2024-11-03T00:47:23+0000, Colin Watson wrote:
> > and the fact that the NAME section has both
es in one go. I do not expect to
ever want to replace that with a shell pipeline.
--
Colin Watson (he/him) [cjwat...@debian.org]
ace some part of a fairly well-optimized
and established C program with a shell pipeline? I'm pretty certain it
would not be faster, at least.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
care would be needed around
error handling and so on. I can see the appeal, in terms of processing
the actual language rather than a pile of hacks that try to guess what
to do with it - but on the other hand this starts to feel like a much
less natural fit for the way nroff is run in every other situation,
where you're processing one document at a time.
Cheers,
--
Colin Watson (he/him) [cjwat...@debian.org]
