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
I'm using the bash-completion-git package from the AUR, which uses the latest code from the master branch. Using the normal bash-completion package which uses version 2.11 doesn't have this issue.
I bisected this down to ca361be. Possibly there should be a special case for .? A similar problem also happens if trying to find completions for a command called .. so if a special case is added for . then one for .. would also be useful. Alternatively maybe just going back to silently ignoring directories would be preferable?
Describe the bug
When trying to find completions for the
.
builtin command, the below messages appear:These messages only appear when trying to find completions for
.
the first time.To reproduce
.
, including the trailing spaceExpected behavior
Completions for the
.
builtin should appearVersions (please complete the following information)
echo "$BASH_VERSION"
: 5.1.16(1)-release(IFS=.; echo "${BASH_COMPLETION_VERSINFO[*]}")
: 2.11.0Additional context
I'm using the
bash-completion-git
package from the AUR, which uses the latest code from the master branch. Using the normalbash-completion
package which uses version 2.11 doesn't have this issue.Debug trace
log.txt
The text was updated successfully, but these errors were encountered: