-
Notifications
You must be signed in to change notification settings - Fork 391
feat: no empty command completion if no_empty_cmd_completion
is on
#978
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
Conversation
95db0b3
to
2a20305
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some other cases where we might suppress command name generations on empty completions.
./bash_completion:2497: _comp_compgen -- -d -c
./completions/_su:23: _comp_compgen -- -d -c
./completions/gdb:23: _comp_compgen -- -d -c
Currently, _comp_compgen_commands
only generates the command names, but maybe it could also generate directories by plusdirs
by default.
Good points. Added The note in gdb completion regarding bash builtins etc being include is valid for quite a few other things as well, that's something we may want to address sometime. |
On some systems, generating the entire list of available commands takes a long time. `no_empty_cmd_completion` is semantically close enough to piggyback on it here. Closes #926
It makes sense to offer completions from explicitly specified paths, too. Thanks-to: Koichi Murase <myoga.murase@gmail.com>
Co-authored-by: Koichi Murase <myoga.murase@gmail.com>
Co-authored-by: Koichi Murase <myoga.murase@gmail.com>
Co-authored-by: Koichi Murase <myoga.murase@gmail.com>
On some systems, generating the entire list of available commands takes a long time.
no_empty_cmd_completion
is semantically close enough to piggyback on it here.Closes #926