> It's a serious annoyance when you're doing build scripts that do stuff like setting $PATH. Indeed, I was bitten by this too. Honestly, its probably the best

> It's a serious annoyance when you're doing build scripts that do stuff like setting $PATH. Indeed, I was bitten by this too. Honestly, its probably the best not to touch PATH and friends and resolve the problem some other way. Or you could use modules. > It also has the annoying "feature" of leaving you in the last directory the script changed to. Yeah, that might be problem. I used to use cd instead of cpush because of this. However, using good framework fixes this. Check out Invoke-Build for your build stuff and you will forget about all of that. Its totally epic. > It may mean there's no way whatsoever to pass a given path to a program. If a program internally doesn't handle quoting and spaces right, you're screwed. Regarding space, this is easily solvable by using short syntax. Regarding quoting, this seems like a less important case - its very rare to have quotes in the file names in my experience.