Timeline for Share environment variables between bash and fish
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2020 at 7:11 | comment | added | Stéphane Chazelas |
Why would you translate spaces to newlines there? Note that the standard tr syntax would be tr ': ' '\n\n' or tr ': ' '[\n*]' here. echo -- $arg... would be more correct, though unlikely to make much difference in practice.
|
|
| Dec 31, 2014 at 16:38 | vote | accept | Tyilo | ||
| Dec 31, 2014 at 16:38 | comment | added | Tyilo | Yay it works now. I don't think any other shell (except fish?) allows paths with colons in PATH anyway. | |
| Dec 31, 2014 at 7:58 | history | edited | ridiculous_fish | CC BY-SA 3.0 |
correct handling of PATH in setenv to split on spaces
|
| Dec 31, 2014 at 7:50 | comment | added | ridiculous_fish | Oh, right, fish will space-separate it inside quotes. I'll update the comment. | |
| Dec 30, 2014 at 0:39 | comment | added | Tyilo |
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.
|
|
| Dec 30, 2014 at 0:35 | comment | added | ridiculous_fish |
[ 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.
|
|
| Dec 28, 2014 at 23:28 | comment | added | Tyilo |
Will the PATH fix for fish work with paths with: spaces? newlines? other things to look out for?
|
|
| Dec 28, 2014 at 21:08 | history | answered | ridiculous_fish | CC BY-SA 3.0 |