Hi Eric,
Eric S. Raymond wrote on Fri, Mar 07, 2014 at 04:03:49PM -0500:
> Kristaps Dzonsons :
>> esr wrote:
>>> The effort required to get this far with mdoc was extreme even for
>>> me. Thus I consider that effort very unlikely to be successfully
>>> replicated - I doubt anyone else will have t
Ingo Schwarze :
> Yes, .Xo/.Xc is slightly ugly, but you don't have to use it if
> you don't like it.
You can't tell me it's optional. It's in the corpus and doclifter has to
cope with it somehow.
> > The result is pure hell for anyone trying to interpret the mess with
> > anything but groff it
Kristaps Dzonsons :
> >The effort required to get this far with mdoc was extreme even for
> >me. Thus I consider that effort very unlikely to be successfully
> >replicated - I doubt anyone else will have the stamina required.
>
> Er... http://mdocml.bsd.lv?
An implementation by the *designer of m
Hi Eric,
Eric S. Raymond wrote on Fri, Mar 07, 2014 at 02:14:24PM -0500:
> I've written an mdoc interpreter. It's in doclifter. And I'm here
> to tell you why mdoc is not the solution you're looking for.
Well, i already solved the problem with it, so you are somewhat
late in warning me... :-D
The result is pure hell for anyone trying to interpret the mess with
anything but groff itself. I believe I am the only person who has
even tried this seriously.
I managed to handle almost all of it, because I am exceptionally good
at the kind of hacking required for the job. But not in fact all
Anthony J. Bentley :
> Funny, that looks almost exactly like what you posted. Since -mdoc
> already exists, is shipped in man(1) with a great many systems
> (certainly all the ones I've ever used), and already has thousands of
> manpages written in it, why extend -man in a backwards incompatible
>
