-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
CLI UX: Flags shouldn't be global #1624
Comments
This is a good request. Originally hugo only had two commands, |
anthonyfok
added a commit
to anthonyfok/hugo
that referenced
this issue
Dec 3, 2015
This is to ensure that only the relevant command-line flags for a certain Hugo subcommand is shown to the end user, reducing clutter and improving user experience. Fixes gohugoio#1624 - CLI UX: Flags shouldn't be global
anthonyfok
added a commit
that referenced
this issue
Dec 11, 2015
anthonyfok
added a commit
that referenced
this issue
Dec 16, 2015
bramp
pushed a commit
to bramp/hugo
that referenced
this issue
Dec 17, 2015
This is to ensure that only the relevant command-line flags for a certain Hugo subcommand is shown to the end user, reducing clutter and improving user experience. Fixes gohugoio#1624 - CLI UX: Flags shouldn't be global
bramp
pushed a commit
to bramp/hugo
that referenced
this issue
Dec 17, 2015
The crash was introduced by commit 00d0477 in PR gohugoio#1652 where access to NoTimes was attempted even though --noTimes was not defined for the config, check and benchmark commands. Special thanks to @bep for the heads-up! See also gohugoio#1624 - CLI UX: Flags shouldn't be global
bramp
pushed a commit
to bramp/hugo
that referenced
this issue
Dec 17, 2015
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
This is to ensure that only the relevant command-line flags for a certain Hugo subcommand is shown to the end user, reducing clutter and improving user experience. Fixes gohugoio#1624 - CLI UX: Flags shouldn't be global
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
The crash was introduced by commit 00d0477 in PR gohugoio#1652 where access to NoTimes was attempted even though --noTimes was not defined for the config, check and benchmark commands. Special thanks to @bep for the heads-up! See also gohugoio#1624 - CLI UX: Flags shouldn't be global
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
v0.15 had it, but I removed it inadvertently for 0.16-DEV in commit 00d0477 in PR gohugoio#1652. Also add directory bash-completion for `--source` for `hugo convert`, `hugo list` and `hugo new`. See gohugoio#1624, gohugoio#1589
tychoish
pushed a commit
to tychoish/hugo
that referenced
this issue
Aug 13, 2017
Reason: The `--source` flag was added back to the `hugo new` commands in commit c1e134f. See gohugoio#1624, gohugoio#1589
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Command line flags should not be global. This is obvious when you look at for example the help for "gen man"; the options don't make sense with that command.
The text was updated successfully, but these errors were encountered: