Consistent bash-completion if a command is not found #1272
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey,
it seems that if a command is not found, the fallback file autocompletion does not work the same as the standard bash autocompletion:
CURRENT
some-cmd folder-na(tab)
->some-cmd folder-name
currently the folder name is inserted, including a space at the end
PROPOSED
some-cmd folder-na(tab)
->some-cmd folder-name/
In the current bash versions the folder name is inserted with a slash at the end, allowing you to chain folder paths
With this change bash will decide how to handle the autocompletion.
tested on
MacOS 10.14
references
https://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html
https://stackoverflow.com/a/22827323