You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With no_empty_cmd_completion off, empty commandlines get no completion, but empty commands in non-empty commandlines do. In particular, this made me think #978 didn't exist -- I'd transpose typing a tab with the first letter of a command after a semicolon, which would trigger command search.
To reproduce
$ shopt -u no_empty_cmd_completion
On an empty command line, press <tab> to attempt to trigger command completion -- nothing happens. That is (with prompt $ ): $ <tab>
does nothing. However $ <tab>
and $ ; <tab>
both trigger completion, as expected.
And of course, with shopt -s no_empty_cmd_completion, all three don't trigger completion.
Expected behavior
$ <tab> should trigger completion with no_empty_cmd_completion off. Ideally, this sensitivity to no_empty_cmd_completion should be documented somewhere other than the source TIL about doc/configuration.md, and that my system's bash-completion doesn't ship the documentation.
Versions (please complete the following information)
Operating system name/distribution and version: Arch Linux 6.11.5-arch1-1
Describe the bug
With
no_empty_cmd_completion
off, empty commandlines get no completion, but empty commands in non-empty commandlines do. In particular, this made me think #978 didn't exist -- I'd transpose typing a tab with the first letter of a command after a semicolon, which would trigger command search.To reproduce
$ shopt -u no_empty_cmd_completion
On an empty command line, press
<tab>
to attempt to trigger command completion -- nothing happens. That is (with prompt$
):$ <tab>
does nothing. However
$ <tab>
and
$ ; <tab>
both trigger completion, as expected.
And of course, with
shopt -s no_empty_cmd_completion
, all three don't trigger completion.Expected behavior
$ <tab>
should trigger completion withno_empty_cmd_completion
off.Ideally, this sensitivity toTIL aboutno_empty_cmd_completion
should be documented somewhere other than the sourcedoc/configuration.md
, and that my system'sbash-completion
doesn't ship the documentation.Versions (please complete the following information)
echo "$BASH_VERSION"
: 5.2.37(1)-release(IFS=.; echo "${BASH_COMPLETION_VERSINFO[*]}")
: 2.13.0 (though in actualitybash-completion-git 2.13.0.r36.gc4885485-1
-- ie built off c488548)Debug trace
(with
bash --rcfile /etc/bash.bashrc; set -x; set -v
to clean the logs)Attempting to produce logs for
$ ; <tab>
fails -- I immediately get prompted:The text was updated successfully, but these errors were encountered: