Changes to your PATH that you make in emacs are not passed up, only down. You needn't worry about it messing up the system path. I prefer to have cygwin in my path anyway (at the end) since I never know what I might want to run. Certainly this is not foolproof but I haven't had any problems yet.
In a message dated 12/6/01 5:02:37 PM Eastern Standard Time, address@hidden writes:
Subj:RE: [h-e-w] cygwin ispell and emacs 21.1
Date:12/6/01 5:02:37 PM Eastern Standard Time
From:address@hidden
To:address@hidden, address@hidden
File:w32-shells.el (4497 bytes) DL Time (32000 bps): < 1 minute
Sent from the Internet
Hi
Sorry, yes indeed the cygwin setup for emacs from the cygwin FAQ fixes the
falt due to the line that i was lacking: (setenv "PATH" (concat
"C:\\cygwin\\bin;" (getenv "PATH"))). I had hoped to avoid adding the cygwin
bin directory to the system environment PATH because when switching between
shells things can get very confusing if you do this - it;s far nicer just to
set up the bash path when the bash shell is started. However, since
ispell.el runs the ispell.exe directly, not via a shell command (bash -c
ispell <file>, for example), the path needs to contain the location of the
cygwinN.dll for cygwin executables to work. It's a shame ispell.el doesn't
launch ispell via a shell command.
jonathan.
ps. please find attached a file which sets up many other things for cygwin,
and adds a shell submenu to the tools menu
|