Skip to main content
The 2024 Developer Survey results are live! See the results
13 events
when toggle format what by license comment
Feb 2, 2020 at 23:44 vote accept le-doude
Dec 14, 2015 at 19:42 history edited Gilles 'SO- stop being evil'
edited tags
Dec 14, 2015 at 19:41 answer added Gilles 'SO- stop being evil' timeline score: 8
Dec 14, 2015 at 19:24 history reopened G-Man Says 'Reinstate Monica'
Gilles 'SO- stop being evil' shell
Dec 13, 2015 at 8:13 comment added G-Man Says 'Reinstate Monica' I don't know zsh, but it looks like you're having a problem with a difference between zsh and /bin/sh.  Try running zsh .workspace-shotcuts.sh; it will probably fail the same as the source command.  Then look at zsh documentation to figure out what you need to change to get it to work in zsh.  Then source .workspace-shotcuts.sh should work.
Dec 13, 2015 at 6:25 review Reopen votes
Dec 13, 2015 at 6:42
Dec 13, 2015 at 6:07 comment added le-doude @Michael Homer, @cuonglm, @msw ... I have tried source, I do not think it fixed much.
Dec 13, 2015 at 6:06 history edited le-doude CC BY-SA 3.0
update after trying suggestions
Dec 13, 2015 at 4:28 history closed Michael Homer
cuonglm shell
Duplicate of How can I make environment variables "exported" in a shell script stick around?, how to set environment variables from a shell script? [duplicate]
Dec 13, 2015 at 4:04 review Close votes
Dec 13, 2015 at 4:31
Dec 13, 2015 at 2:56 comment added msw I think the problem may be that variables set or exported in a script cannot alter the calling (parent) environment. See stackoverflow.com/questions/8604462/… for example.
Dec 13, 2015 at 2:47 review First posts
Dec 13, 2015 at 3:39
Dec 13, 2015 at 2:39 history asked le-doude CC BY-SA 3.0