Closed
Conversation
Collaborator
tertsdiepraam
left a comment
There was a problem hiding this comment.
Thanks! I don't this is quite right, although it is an improvement. The problem is with complex expressions like:
env expr \( substr hello 2 world \) '&' boop
So substr (and any other keyword) does not need to be the first argument necessarily.
|
GNU testsuite comparison: |
Contributor
|
Closing this PR because it's fixed in #5578 |
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
3 participants
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.
Fixing error message for
Token::PrefixOptokens when they are not the first token in the command line - in line with GNU behavior.And updated tests