-
Notifications
You must be signed in to change notification settings - Fork 238
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
Beautify command line help output #78
Comments
Excellent suggestion. Txs. |
oleg-shilo
added a commit
that referenced
this issue
Jul 25, 2017
oleg-shilo
added a commit
that referenced
this issue
Jul 25, 2017
oleg-shilo
added a commit
that referenced
this issue
Jul 25, 2017
oleg-shilo
added a commit
that referenced
this issue
Jul 25, 2017
Done. Thank you for sharing your code. It provided an excellent opportunity to improve CLI support. I have used a slightly modified version of your |
oleg-shilo
added a commit
that referenced
this issue
Aug 4, 2017
Minor usability improvements * Added System.dll auto-referencing on EnableDbgPrint:true to allow regular expressions to be used in auto-injected dbg.cs. * Issue #78: Beautify command line help output * Issue #71: Issue with multiple indirect relative paths * Added ResolveRelativeFromParentScriptLocation for ALL non absolute paths in //css_import
Great, looks very good now :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggesting to limit the command line help's text width to the console width, in order to prevent line breaks and improve readability.
Some ideas taken from my own ArgsHandler making use of StringEx:
Console.Out.Write(GetHelpText(Console.WindowWidth - 1)); // -1 ensures that lines that exactly match the number of characters do not lead to an empty line (due to the NewLine which is added).
string GetHelpText(int maxWidth)
string SplitIntoLines(int maxWidth, int indent, string text)
The text was updated successfully, but these errors were encountered: