Bash does not like '-' in function names#573
Merged
Merged
Conversation
Member
|
Thanks so much for working on this, @kennyyork! It looks like we're already escaping in this way for |
4135438 to
5b921a0
Compare
Member
|
@swift-ci Please test |
5b921a0 to
f57bea9
Compare
f57bea9 to
fed6a9b
Compare
Member
|
@swift-ci Please test |
This file contains hidden or 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
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 a ParsableCommand has a
commandNamevalue with a hyphen, the bash completion generator will generate a function name with a hyphen which isn't valid in BASH, eg_programName_command_sub-command': not a valid identifierChecklist