I am off-topic.
Ingo Schwarze wrote in
<20200625214812.gf90...@athene.usta.de>:
|given that two authoritative manual pages for the mdoc language
|exist that describe exactly the same language, but in a somewhat
...
| The manual page groff_mdoc(7): https://man.voidlinux.org/groff_mdoc
|
Hi,
given that two authoritative manual pages for the mdoc language
exist that describe exactly the same language, but in a somewhat
different style, an anonymous coward calling himself "B 9" just
suggested in passing in a remark in a bugtracking ticket that it
might occasionally help users if
Follow-up Comment #7, bug #58653 (project groff):
> I had thought you were linking to the mdoc documentation that comes with
BSD.
mandoc is portable software. It is included and used by default in these
systems (chronological order by first official use): OpenBSD, NetBSD, Illumos,
Void Linux,
Follow-up Comment #6, bug #58653 (project groff):
[comment #5 comment #5:]
>
> > This mandoc mdoc(7) you are speaking of,
> > is it part of groff? I don't see it.
>
> No it isn't.
> I already posted the hyperlink: https://man.openbsd.org/mdoc.7
> It is part of mandoc.
Please pardon my
Follow-up Comment #5, bug #58653 (project groff):
> Good documentation lets people know right away what the
> cost of learning will be and what the benefits are.
Right, that's usually the first one to three sentences in a manual page. No
need for a separate document.
In groff_mdoc(7), the
Follow-up Comment #4, bug #58653 (project groff):
[comment #3 comment #3:]
> You say "but beginners need something simpler". I contest that. It's not
because i'm an expert on mdoc(7). When learning a completely new language
totally from scratch, i typically go for the formal standard / formal
Follow-up Comment #3, bug #58653 (project groff):
You say "i wish you had mentioned this before". Granted, it would have been
helpful, and i wanted to. But there isn't time to answer all questions i
could usefully respond to, so it fell through the cracks. I estimate roughly
80% fall through
Follow-up Comment #2, bug #58653 (project groff):
[comment #1 comment #1:]
> I *VERY* strongly oppose this idea.
Thank you, Ingo, although I do wish you had mentioned this on the mailing list
when I first brought it up or at the point when someone else suggested that
the groff project needs to