Skip to content
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

Add man page #46

Open
nitrocode opened this issue Jun 22, 2022 · 2 comments
Open

Add man page #46

nitrocode opened this issue Jun 22, 2022 · 2 comments

Comments

@nitrocode
Copy link

request

This is a nice tool but could you also add a man page to the tool? I ask because it's so handy to run man viddy to get docs like examples to run quickstart commands and the keymaps would be handy.

references

@abhaysp95
Copy link
Contributor

Hmm, few questions I have regarding this:

  1. I don't see that much need of man page. viddy --help proves to be sufficient, I think (but that's not the point, right ?)
  2. What content exactly do you want to be added in man page. I mean, the tool itself isn't having something complicated which would take multiple lines to explain, right ? So, I can't think of anything which will not be redundant.
  3. How should it be generated ? Using some go package dependency like md2man or using n/t/g/roff or any other idea ?

@Nudin
Copy link

Nudin commented Jan 21, 2023

A few thoughts from me:

  • It bugs me that for some commands I have to look into man, for some I have to call -h, for others -? and even others --help – in my opinion it is good UX to provide all of them to spare the users from wasting time.
  • A man page is usually a longer documentation than what -h gives (especially sine viddy -h currently only prints very spare information)
  • Viddy -h currently does not at all tell what viddy is/does.
  • Viddy -h does not provide a link to the website (or github repo) of the project (nor does viddy -v)
  • To see the keybindings I have to press h in a running viddy. So the documentation is split across two places and I have to guess that h in viddy might show more information.
  • The configuration path and format is only docuemented in the repo. Nowhere else
  • Man pages have a normalized formatting and by convention a similar structure. This helps to easily find the right information, even in moments of stress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants