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
Shell completion is suggesting aliases #1875
Labels
area/v3
relates to / is being considered for v3
kind/feature
describes a code enhancement / feature request
kind/question
someone asking a question
Comments
bartekpacia
added
area/v2
relates to / is being considered for v2
kind/question
someone asking a question
status/triage
maintainers still need to look into this
labels
Mar 11, 2024
This is not really a bug as much as it is a desired behaviour. |
Can we mark it as |
dearchap
added
kind/feature
describes a code enhancement / feature request
area/v3
relates to / is being considered for v3
and removed
area/v2
relates to / is being considered for v2
labels
Apr 16, 2024
meatballhat
changed the title
BUG: shell completion is suggesting aliases
Shell completion is suggesting aliases
Apr 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/v3
relates to / is being considered for v3
kind/feature
describes a code enhancement / feature request
kind/question
someone asking a question
My urfave/cli version is
v2.27.1
Checklist
Dependency Management
My project is using Go modules.
Describe the bug
My program called
emu
is built with this great module. Let's sayemu
has the following commands:kill
run
list
The
list
command also has an aliasls
.The problem is that both
list
andls
are shown in shell completion ("TAB completion"), which doesn't make much sense and is annoying:emu.mov
To reproduce wrong behavior
Expected behavior
Aliases are not shown in shell completion. This is how huge, popular CLI projects like
gh
ordocker
do it:Screen.Recording.2024-03-11.at.01.53.36.mov
(in Docker's case,
ls
is the main command andlist
is an alias - so my point is still valid).Want to fix this yourself?
Sure!
Run
go version
and paste its output hereRun
go env
and paste its output hereThe text was updated successfully, but these errors were encountered: