5 ms·
What's worse, Linux (or Unix) requires the user to re-login to make the changed environment variables take effect. Whereas in Windows they are applied immediate
by yokohummer7 11y ago
What's worse, Linux (or Unix) requires the user to re-login to make the changed environment variables take effect. Whereas in Windows they are applied immediately, so you don't have to re-login after changing PATH.
- hikarudo 11y agosource ~/.bashrc
- anon4 11y agoAnd this will change it for programs I launch by clicking on the launcher menu?
- cosarara97 11y agoYou could have the launcher source your .profile/.env/whatever on every app launch. Count it as a bug in your launcher ;)
- Dylan16807 11y agoActually Explorer manually reloads environment variables when you change them, and nothing else is affected.
- yokohummer7 11y agoThat's a neat trick, thanks for pointing me out. I've always wondered how Windows could have accomplished that. It's a shame that Linux doesn't have such an equivalent. If we are to do the same thing in Linux, a login shell (bash or zsh or even GNOME) would be the right place to implement?
- MatmaRex 11y agoThere's a recent post from Raymond Chen about this, actually: http://blogs.msdn.com/b/oldnewthing/archive/2015/09/15/10641604.aspx http://blogs.msdn.com/b/oldnewthing/archive/2015/09/15/10641...
- frik 11y agoThe same on both system. You have to stop and start cmd.exe/etc again. In older Windows versions you had to reboot/re-login.