Open
Conversation
Under OS X, you can't do `. <(echo whatever)` - it just fails. Looks to be a bug in OS X's version of bash. Workaround: use a tempfile.
Member
|
This looks good to me -- seems like in general, we can use a tempfile instead of using the I think it would be worth making it clear in the README that you may need to do what you ended up doing in your bashrc if you're on OS X. There is an OS X troubleshooting section that might be a good place, maybe with a little footnote linking to it in the place where we advise putting |
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.
This doesn't fix everything.
zerkenv module1 module2still chokes. But it basically works. I have this in my.bashrc, since the same problem this patch fixes means you can't do. <(zerkenv -i bash).