@kat@yarn.girlonthemoon.xyz On the one hand, all these programs have a very long history and the technology behind manpages is actually very powerful â you can use it to write books:
https://www.troff.org/pubs.html
I have two books from that list, for example âThe UNIX programming environmentâ:
https://movq.de/v/c3dab75c97/upe.jpg
Itâs a bit older, of course, but it looks and feels like a normal book, and it uses the same tech as manpages â which I think is really cool. đ
Itâs comparable to LaTeX (just harder/different to use) but much faster than LaTeX. You can also do stuff like render manpages as a PDF (man -Tpdf cp >cp.pdf
) or as an HTML file (man -Thtml cp >cp.html
). I think I once made slides for a talk this way.
On the other hand, traditional manpages (i.e., ones that are not written in mandoc) do not use semantic markup. They literally say, âthis text is bold, that text over here is italicsâ, and so on.
So when you run man foo
, it has no other choice but to show it in black, white, bold, underline â showing it in color would be wrong, because thatâs not what the source code of that manpage says.
Colorizing them is a hack, to be honest. Youâre not meant to do this. (The devs actually broke this by accident recently. They themselves arenât really aware that people use colors.)
If mandoc and semantic markup was more commonly used, I think it would be easier to convince the devs to add proper customizable colors.