Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    Will the PATH fix for fish work with paths with: spaces? newlines? other things to look out for? Commented Dec 28, 2014 at 23:28
  • [ is a builtin in both bash and fish, so PATH should not need to be set correctly to use [. The setenv sample should work with all characters in PATH except for colons and newlines. Commented Dec 30, 2014 at 0:35
  • Replacing tr with /usr/bin/tr I and using the .env file provided in my question, I get a lot of errors when starting fish. I don't think the PATH handling is correct. Commented Dec 30, 2014 at 0:39
  • Oh, right, fish will space-separate it inside quotes. I'll update the comment. Commented Dec 31, 2014 at 7:50
  • Yay it works now. I don't think any other shell (except fish?) allows paths with colons in PATH anyway. Commented Dec 31, 2014 at 16:38