Conversation
its absolutely maddening learning just how semantically rich modern manfiles are yet because we render them in less, none of it gets displayed
1
0
0

@coolbean wait what, how am i supposed to read em then?

1
0
1
@desea thats the thing, less is the intended way and the only real alternative is html which is a gigantic pain in the ass without a dedicated browser plugin

but yea mdoc and roff contain so much semantic information that doesnt get rendered its just maddening. also links dont work and that alone is really annoying tbh

also the lack of tables of contents for jumping to the section you need is really annoying for super large ones like ksh(1)
1
0
1
@coolbean @desea i think luke smith was shilling roff as a whole latex replacement
1
0
1
@snacks @desea god of course he would do that

technically the tex equivalent to manpages would be gnu info which i do also respect a fair bit
1
0
1
@snacks @desea mostly cause they actually have working hyperlinks between pages and the concept of structuring multiple pages into something larger, neither of which is supported under man much to my dismay
1
0
1
@desea @snacks concept: smdoc (structured mdoc, definitely not sado-masochistic documentation) that keeps 'manpages' inside greater 'manbooks' that function more similarly to info files (with regular unix manpages mostly falling in a manbook id call "Operating System")
1
0
1
@desea @snacks alternatively: just let people add arbitrarily named non-numeric man sections (and write index pages for them)
1
0
1
@desea @snacks yea this is probably the sanest approach to such an idea
0
0
0