Fixed bug where IFS shell var would get set to empty string #427
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
ghost
assigned 
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.
I have tested the old version and seen the problem, then tried with this new version, and the problem is gone.
IFS info: http://stackoverflow.com/questions/16719770/what-can-change-command-substitution-behavior-in-bash and http://www.gnu.org/software/bash/manual/html_node/Word-Splitting.html
The bug was that after source-ing the setup.bash my IFS shell var would be set to the empty string, which means it does NO word splitting. The original behavior is when IFS is UNSET which means split on any white space.