Fix bad math expression error when IFS doesn't contain space #85
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
When the previous prompt contains highlight and IFS doesn't contain space, calling filter-select results in the following error: filter-select:136: bad math expression: operator expected at `14 fg=blue...' This is fixed by specifying the delimiter for the read command.
|
Thanks. Sorry for the delay. |
|
Thanks for merging! |
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.
When the previous prompt contains highlight and IFS doesn't contain space, calling filter-select results in the following error:
Since the
readcommand has the-doption to specify the delimiter, I think it's safer than relying on the user'sIFS, which in my case was$'\n'.