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.

Sign up for GitHub

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

Jump to bottom

Do global options really need to be required? #35

Closed
jwhitlark opened this issue Oct 22, 2018 · 4 comments
Closed

Do global options really need to be required? #35

jwhitlark opened this issue Oct 22, 2018 · 4 comments
Labels
starter issue Good for newcomers

Comments

@jwhitlark
Copy link
Contributor

Can just specify it as empty, but it can take a few minutes to figure out what the problem is, especially for those less familiar with spec.
@l3nz
Copy link
Owner

l3nz commented Oct 25, 2018

Makes sense to leave them out where not needed.

@l3nz
Copy link
Owner

l3nz commented Oct 28, 2018

While we work on that, if the are missing or empty, it makes no sense to print them out:

USAGE:
 eml [global-options] command [command options] [arguments...]

but

USAGE:
 eml  command [command options] [arguments...]

@l3nz l3nz added the starter issue Good for newcomers label Jan 1, 2019
@thiru
Copy link

thiru commented Apr 8, 2019

It's common for terminal apps to be called like app --version to print the version. Is this possible?

@l3nz l3nz mentioned this issue Apr 10, 2019
Open
l3nz pushed a commit that referenced this issue Nov 3, 2019
Fixing #35 - :global-options not required if empty.
7a2bd99 
We already injected default options on reading, so
I basically extended the SETUP-DEFAULTS def that
was already there..... :)
@l3nz
Copy link
Owner

l3nz commented Nov 3, 2019

So closed in 0.3.9

@l3nz l3nz closed this as completed Nov 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
starter issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jwhitlark @thiru @l3nz