Fixes {} parsing inside shell scripts #4288
Merged
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
1 task
merceyz
pushed a commit
that referenced
this pull request
Oct 21, 2023
* Fixes {} parsing inside shell scripts
* Adds tests
* Compiles grammar
(cherry picked from commit a2cf91a)
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.
What's the problem this PR addresses?
We didn't support passing
{}into shell arguments.Fixes #2670
How did you fix it?
Just a matter of removing
{of the list of special characters (so we can writeecho {orecho {foo), and adding a special case for{}(so we can writeecho {}orecho foo{}). It seems thatecho }isn't valid in zsh, so I didn't try to support it.Checklist