News for hackers. Stuff that matters.

A comment on Environment Variables and Path in Windows 10. Parent comment

Re:Environment Variables and Path in Windows 10 by barrkel on Monday October 26, 2015 @06:42AM (#10450518)
If the aim is to replicate how Windows works, only the GUI shell would need to reload environment variables (i.e. the process that forks when you start programs using whatever the desktop's idiom is).
[ Parent | on HN ]
Re:Environment Variables and Path in Windows 10 by lottin on Monday October 26, 2015 @07:04AM (#10450601)
This seems inconsistent behaviour to me. Some running processes reload the environment and others don't. Maybe in Windows they can get away with it, but that doesn't mean it's a good idea.
[ Parent | on HN ]
Re:Environment Variables and Path in Windows 10 by darklajid on Monday October 26, 2015 @08:15AM (#10450843)
To be fair: The Windows way is kinda consistent: If the environment definition was changed, everyone gets a window message. It's just that no one but explorer.exe cares about that and reacts, as far as I'm aware (Raymond Chen had a recent article mentioning exactly this).

So, the OS tells everyone 'Hey, you totally could update your environment'. But your running instance of Skype or whatever just doesn't need to care.

[ Parent | on HN ]
Re:Environment Variables and Path in Windows 10 by zastrowm on Monday October 26, 2015 @10:39AM (#10451726)
Raymond Chen article for anyone that is interested: http://blogs.msdn.com/b/oldnewthing/archive/2015/09/15/10641...
[ Parent | on HN ]
Re:Environment Variables and Path in Windows 10 by majkinetor on Monday October 26, 2015 @08:34AM (#10450934)
I think that reacting to system change is opt-in.
[ Parent | on HN ]