-
Notifications
You must be signed in to change notification settings - Fork 418
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
CommandLine.setSeparator() is ignored when generating usage text. #184
Comments
Thanks for looking at picocli. You are correct. This behaviour is documented in the user manual. Basically, the The idea was to allow users to separately control the usage help and the parser separator. |
I realize now that this could be confusing, but on the other hand I would like to support allowing users to separately control the usage help and the parser separator. I just saw that the javadoc on I hope that will be sufficient, what do you think? |
…ffects parsing only and link to the `@Command` `separator` annotation attribute.
Updated the javadoc. |
I have come to my senses after realizing I could not think of any scenario where it would be useful for users to have a different separator in the parser and the usage help. The current behaviour is just confusing. I will make changes such that the separator set programmatically via |
Title says it all. A call to
cmd.usage(system.err)
will print the default or annotated separator and ignores the value set bycmd.setSeparator("XXX")
.The text was updated successfully, but these errors were encountered: