Default to filename completion if no other matches are found #186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tschaub I like this a lot, let the bash do what it's good at 👍 |
|
0765cbc guards against bad output when trying to complete an option that doesn't match any configured options. Let me know if you'd like these squashed. |
|
|
||
| # if no match was found, fall back to filename completion | ||
| if [ ${#COMPREPLY[@]} -eq 0 ]; then | ||
| COMPREPLY=( $(compgen -f -- "${cur_word}" ) ) |
bcoe
added a commit
that referenced
this pull request
Jun 23, 2015
Default to filename completion if no other matches are found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If calling a script with
--get-yargs-completionsdoesn't result in any matches for the current word, we can fall back to the default filename completion.See suggestion in #180 (comment).