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
Use long options instead of short ones #1349
Conversation
I marked this as stale due to inactivity. → More info |
Hmmm ... thanks @Stale to poke me. Will check soon. |
So the quickstart (and more?) are moved from .xml into .md Commit: e0ea3c8 [e0ea3c8] which got merged in Commit: b721877 [b721877] |
I marked this as stale due to inactivity. → More info |
Not sure how to trigger tests :-/ |
I don't think tests are really relevant to such a trivial documentation change. I'm personally not sure if using long forms is preferable in docs. Perhaps some of "real" maintainers have a strong opinion on this. If I wanted to learn what the options mean, I'd look into the corresponding man page. And when I type into console I almost always use the short options. In scripts I would probably prefer long ones, though... |
If you don't want to help new users onboarding please do keep the short options in the documentatation. Making them long would have helped me a lot faster learning new/unfamiliar tools. |
This seems like a good idea. Start with long, and once you get tired of typing, switch to old. |
@clemens-tolboom sorry for the long waiting time. Are you still interested in merging this? Please rebase so we can proceed. |
@fricklerhandwerk I pass ... I removed my clone and am not using nix anymore. I rerolled it Feb 13, 2021 hope someone can redo this on |
Behold, everyone, how we've abandon PRs chasing people off! May we finally be turning a new leaf. |
#7864 I have rebased it. |
It is a little hard to learn what the options mean.