Hi, I've just installed a compact sans font (from
http://input.fontbureau.com/ ) and manual pages started to look broken.
As you can see in the screenshot (man 2 control), there are white spaces
that looks like tabs in the middle of the text with apparently no reason.
Even in the troff source
Interestingly enough the problem disappears with a mono font.
I suspect that troff is inserting such tabs instead of spaces when it
thinks they are the same. Indeed libframe (as far I could understand from
the manual and the sources) properly handles such variable width fonts.
Looks like I've to
On Wed, Mar 4, 2015 at 5:13 PM, Giacomo Tesio giac...@tesio.it wrote:
why the hell we still use troff for manual pages?
What do you propose we use instead?
--
Aram Hăvărneanu
Well... docx, obviously! :-D
Seriously, a markdown/asciidoc like language would be far easier to
write and update.
We could even compile it to troff, we we had to print it.
However, this is not a rant specific to plan9. Linux is not better
from this point of view.
Giacomo
2015-03-04 22:31
troff is great. easy to maintain programmatically.
sl
2015-03-05 0:56 GMT+01:00 s...@9front.org:
And btw, programs don't write man pages... yet.
Are you familiar with the conventions that power godoc?
No, but I know quite well it's predecessors (Docstrings, Javadoc etc...).
They are great for API, but IMHO not every unix man page can be
Well, while a bit offtopic... what do you mean by programmatically.
And btw, programs don't write man pages... yet.
Giacomo
2015-03-04 23:39 GMT+01:00 Stanley Lieber s...@9front.org:
troff is great. easy to maintain programmatically.
sl
Well, while a bit offtopic... what do you mean by programmatically.
Programmatically = using a program.
If you arrange your troff sources in a thoughtful way, you can perform
changes using scripts or other programs without needing to stare at each
line of source individually. (I realize that
