Unix in Windows; ranting about Cygwin
Jan. 30th, 2010 06:34 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
If I get a lesson from a Cygwin whiz, I may be able to avoid the cost of switching OSs...
My PATH variable often seems to be broken. The space inside "Program Files" causes parsing problems, but you can't tell how far it's parsed, except by painstakingly looking inside those directories and trying to run files in them.
On top of this, whenever you make a change to the default values of environment variables, you always need to start a new shell to see the change. I wish I could set these defaults in a configuration file.
My Emacs often forgets that my SHELLOPTS has "igncr" and thereafter sends "\r" to the shell with every CR, becoming useless and forcing me to kill it.
My R shell seems to run in a different environment altogether, and does not recognize the PATH that my bash shell does (both running inside the same Emacs window).
Should I blame Cygwin?
My PATH variable often seems to be broken. The space inside "Program Files" causes parsing problems, but you can't tell how far it's parsed, except by painstakingly looking inside those directories and trying to run files in them.
On top of this, whenever you make a change to the default values of environment variables, you always need to start a new shell to see the change. I wish I could set these defaults in a configuration file.
My Emacs often forgets that my SHELLOPTS has "igncr" and thereafter sends "\r" to the shell with every CR, becoming useless and forcing me to kill it.
My R shell seems to run in a different environment altogether, and does not recognize the PATH that my bash shell does (both running inside the same Emacs window).
Should I blame Cygwin?