On Sun, Jul 24, 2022 at 11:11:10AM -0500, G. Branden Robinson wrote: > At 2022-07-24T15:45:46+0000, DJ Chase wrote: > > On Sun Jul 24, 2022 at 8:06 AM EDT, G. Branden Robinson wrote: > > > At 2022-07-24T03:17:44+0000, DJ Chase wrote: > > > > I???ve never read the Texinfo manual; I learned *roff through Unix > > > > For People,[1] then various online materials maybe half a year > > > > ago. The turn-off for me was how cryptic all of the troff examples > > > > (from any source) I saw were, and how it felt like I was always > > > > fighting the typesetter to get it to do even basic things. > > > > > > As someone who's done a lot of work on the Texinfo manual (and other > > > groff documentation) over the past 5 years, that is disappointing to > > > hear. > > > > I just read some of it. I wish I read it when it felt like I was > > fighting with the typesetter ??? it???s very helpful. > > I should correct myself. I've only been hacking on our Texinfo manual > for about 4 years, so if you're looking at the one from groff 1.22.4, I > deserve no credit for any helpful material you find there. (There was > already an immense amount!)
Am I the only person who thinks that have *roff documentation in a different markup is crazy? I wrote a couple source management systems, this is like I was storing BitKeeper in Git. That says I trust Git but not my own code. Has anyone proposed redoing the texinfo stuff in Groff? If not, why not?
