Repository navigation
Autocomplete after double dash (--) executing command action. #1993
Description
Activity
- addedarea/v2relates to / is being considered for v2relates to / is being considered for v2kind/bugdescribes or fixes a bugdescribes or fixes a bugstatus/triagemaintainers still need to look into thismaintainers still need to look into this
on Oct 24, 2024 @AaronLieb Yes this is similar to #1916 . I have a fix for this in v3. Let me see if I can backport to v2. Thanks for reporting
No the fix is in PR #1919 .
@AaronLieb Would you be able to test the PR in #1919 to see if it fixes your issue ?
@AaronLieb I looked at v2 and its more complicated to fix there. Not sure if I have the bandwidth to do it for v2. If you end up doing a PR I will be glad to review.
@dearchap I'll see if I have some time today to test the v3 fix and push out a v2 PR.
My experience with this library and go experience in general is pretty limited, so if I push out a PR, feel free to give plenty of criticisms.
@dearchap the latest v3 alpha version with the v3 fix has an unverified commit and was incorrectly added to go.pkg.dev. The creation date is incorrect, isn't marked as the latest version, and fails the checksum when running
go get github.com/urfave/cli/v3@v3.0.0-alpha10. Please fix the release and let me know once you've done so.I'm working on the v2 fix
@AaronLieb fixed the 3.0.0-alpha10 release issue. Please check
@dearchap appears the checksum is still failing when running
go get github.com/urfave/cli/v3@v3.0.0-alpha10@meatballhat can you take a look ?
Reacted by Dan BuchIf you want to use the latest
v3release, then I recommend:import "github.com/urfave/cli/v3"
and then
go mod tidyandgo get -uwill get the correct latest in that series (currentlyv3.0.0-alpha9.1) and skip over the bogusv3.0.0-alpha10.Please let us know if this isn't working for you, or if you're unable to use this solution 🙇🏼
9 remaining items
- addedarea/v3relates to / is being considered for v3relates to / is being considered for v3
on Jun 28, 2025 Hey, I just spend some time investigating this problem (completion not working for flags if I type
--and then<TAB>) and was going to write a new issue, but found this one instead – nice.Not sure what the expected behavior should be here. Ideally, it should autocomplete all of the long flags
I think I disagree with PR #1938 – it essentially broke shell completion for flags.
if this is the case, should the PR be reverted?
Reacted by Tim SoethoutI agree with expecting autocompletion options when typing
--<tab>, potentially including the--itself as valid completion.
I can confirm this behavior on bash 5.3 with v3 (v3.6.1) as well.Reacted by Andy BrodyThis appears to affect the Spacelift
spacectlCLI, which uses v3.4.1. spacelift-io/spacectl#361I'm not familiar with the code here, so take this with a grain of salt, but IMO the approach of appending
--generate-shell-completionseems quite fragile. I might suggest the fix should use a separate subcommand instead of an option, so there's less danger of accidentally executing the underlying command.So when completing after
cli foo --bar, it might run:cli __complete foo --barInstead of the existing
cli foo --bar --generate-shell-completionReacted by Tim Soethout and gcooktns@ab that's a fantastic suggestion. Unsure why we couldn't have done it this way. I have to dig into the history and investigate
@bartekpacia If I make this change would it be considered a breaking change ? If so we would need to release it as v4
@dearchap I assume this could also be non-breaking as an internal option when enabling the shell completion? So you could have the old behaviour in v3 but an additional
EnableBashCompletionAsArg: trueand in v4 you make that one a noop.- added a commit that references this issue
on Aug 6, 2026 - added a commit that references this issue
on Sep 4, 2026 - added a commit that references this issue
on Sep 13, 2026 - added a commit that references this issue
on Sep 20, 2026
My urfave/cli version is
v2.27.5
Checklist
Dependency Management
Describe the bug
If Bash completion is enabled, and the user attempts to tab complete after a double dash (--), it will execute the normal command action.
To reproduce
Describe the steps or code required to reproduce the behavior
main.go
using the v2 zsh_autocomplete
Sourcing it as such in my ~/.zshrc
mkdir /tmp/cli_test/ && ls /tmp/cli_testDir is empty
Try autocomplete
Check dir
TestFile.out is present
Observed behavior
Due to the double dash (--), the
--generate-bash-completionflag was treated as an argument, and the command was executed normally. This behavior is INCREDIBLY DANGEROUS as it can cause premature execution of a command, without even pressing enter!Expected behavior
There are several ways this could be handled.
The ideal solution would be autocompleting the list of long flags, instead of executing the normal command action
Another solution would be preventing the command from being executed and not autocompleting.
Additional context
This problem was introduced by this PR
#1938
I personally disagree with this PR being marked as a bug instead of a feature, and think that this behavior should be toggleable instead of enabled for all cli applications.
This PR did disable bash autocomplete after a double dash, but introduced a much worse issue, which is executing the command normally...
Want to fix this yourself?
If I find time, I may be willing to fix this myself, but I wanted to report this as soon as possible since this bug could cause severe damage in the worse case scenario.
Run
go versionand paste its output hereRun
go envand paste its output here