Conventional formatting and some fixes for man page #21
No reviewers
Labels
No labels
bug
dependency
documentation
duplicate
enhancement
fixed
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bud/typiskt!21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "manpage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
Use
.OPmacro in the SYNOPSIS section which will handle the font aswell as the page width.
Use macros like
.B,.Iand.BRinstead of inline escapes.Use
.TPinstead of.PPin the OPTIONS section, which will handle theindentation and the first line-break.
Change orientation of the table to maintain page width.
Added missing newline in the table formatting for the "excercises" mode.
Add COPYRIGHT section with licesne.
Hello @Mudskipper875 Thanks for the PR!
I think your version of the manpage is much better than the autogenerated ones.
however, the manpages for all my projects are autogenerated from markdown documents by
go-md2manorlowdown. And the content of the manpages are shared with other parts of the project (README.md, output of--help, wiki).I am actually currently in the process of updating my homebrewed buildystem (budlabs/bashbud) and all my projects that uses it. And since the manpage is autogenerated, they will no longer be included in the repositories (instead generated with other documents via
make).So, I will merge this, but. I will also soon update this repo, where no manpage is included, and sadly, the generated one will be as bad as the one you have fixed.
Oh I see. Thanks anyway!