-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Nicer help message #37
Comments
I will admit copy writing is not my strong point. I will have to see about wrapping. Its done though https://github.com/urfave/cli and I don't remember a way to do it in an automated way, but perhaps newlines will work. If you want to submit a PR with redone messages id be happy to merge it in. Otherwise I am afraid my best guess might still be awkward. Let me know either way and ill look into the wrapping. |
Have modified some of the copy as suggested. Not sure if I can modify the wrapping, still investigating this. |
|
That's a lot clearer. The only big issue I still have with it is for |
Dammit I had a feeling I might have missed one. Ill update that as well. |
Done. |
The help message produced by
scc
is somewhat confusing and hard to read.The help text is currently 170 columns wide. It could benefit from line wrapping, ideally automatic based on terminal width, but I understand if that's out of scope.
Current:
Wrapping for 100 columns:
In addition, many of the help messages are phrased awkwardly, which makes the width issue worse.
For example,
--files
has the description "Set to specify you want to see the output for every file" which could be written more concisely as "Display output for every file".The text was updated successfully, but these errors were encountered: