msn page / web reference / README.md #83
Labels
No Label
bug
compatibility
documentation
duplicate
enhancement
future release
help wanted
invalid
non-code
question
refactor
testing
this release
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cmccabe/linkulator2#83
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
I created a linkulator.1.html webpage, somewhat in man page style, and added it to the repo. It is also, for now, hosted at https://rawtext.club/~cmccabe/linkulator.1.html
We should create a master reference page (in markdown?) that can be converted to man page, webpage and README file formats -- or at least, with content that can be used across these formats so that they are consistent. The webapage does not need to remain in man page format; I just did it to see what it would look like.
I like this idea. Reusing as much as possible would save time and effort.
These documents tend to have different purposes - a man page is like an instruction booklet, and probably does not include installation instructions like the README.md would. What are your thoughts as to how this could be managed?
It seems like if it was done in markdown as a man page, installation instructions, and background info/faq/misc that a script to cat them together into various forms and convert to final formats could be written up. Not sure if that over-complicates or not.
I use
txt2man
to help get manpages started... there may be a version or something similar that will convert from markdown. Not sure.Maintaining segments in markdown that can be combined and converted to the right format seems good to me, and not too complicated.