-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
man page bad #150
Comments
I agree with your criticism (though I don't think it impacts the usefulness of the manpage that much)
That is why I plan to start using a tool like asciidoctor to generate the |
While I recommend learning a little troff and -mdoc (for example with
<https://manpages.bsd.lv/mdoc.html>), using a different language might
also yield acceptable, even though not great, results. So that’s fine,
I guess.
|
https://github.com/rtomayko/ronn may be another good alternative to write the man page source |
Here's another option for translating a flavor of Markdown to a manual page https://manpages.debian.org/testing/scdoc/scdoc.5.en.html |
rlwrap(1) is a bad man page:
\-
—“minus”—isused instead
\-
is usednothing of that sort (eg., in NAME) and where there should be
paragraph breaks, ie.
PP
name) and inconsistent (sometimes without the blank)
sometimes don’t have two blanks following
"
It is very valuable that it exists, but I’d like to stress that the
man page as-is, without talking about its content, is really, really
terrible, both in input and output.
I don’t know how such a man page could come into existence. It looks
kinda generated, but then too inconsistent for that.
Before fixing it, I’d like to hear your input on why it is that way,
as well as any special wishes (Can I use -mdoc, or does it need to
stay at -man? Em-dashes or en-dashes? If -man, options with
hyphen-minuses (as is arguably correct) or with wrong
\-
? Or do youstraight-up don’t care and NACK right away?).
The text was updated successfully, but these errors were encountered: