To verify it, all you have to do is open a bash prompt (Cygwin.bat,
mintty, rxvt, whatever) and then launch a cmd.exe or powershell.
Check the path in the bash prompt and you will see the cygwin stuff at
the beginning of it.
Check the path in the cmd.exe or powershell prompt which was run
*after* the bash script updated the path and you will see that it does
*not* include the cygwin paths.
Well, I just (gasp) tested! And awful lot of bandwidth wasting is being done
by people who think they know how it works. But for me, at least, the path
from the invocation of cmd was the same as the path in the Cygwin session
from which it was invoked. Thus:
0/tty2W0(2)$ echo $PATH
/home/lmaschm/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Program
Files/Common Files/Microsoft Shared/Windows Live:/c/WINDOWS
/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/WINDOWS/system32/WindowsPowerShell/v1.0:/c/Program
Files/Common Files/Microsoft Sha
red/Windows Live:/usr/lib/lapack
0/tty2W0(2)$ cmd
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\cygwin-1.7\home\lmaschm>path
path
PATH=C:\cygwin-1.7\home\lmaschm\bin;C:\cygwin-1.7\usr\local\bin;C:\cygwin-1.7\bin;C:\cygwin-1.7\bin;C:\cygwin-1.7\usr\X11R6\bin;C:\P
rogram Files\Common Files\Microsoft Shared\Windows
Live;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\
WindowsPowerShell\v1.0;C:\Program Files\Common Files\Microsoft
Shared\Windows Live;C:\cygwin-1.7\lib\lapack
C:\cygwin-1.7\home\lmaschm>exit
exit
0/tty2W0(2)$
--
Lee Maschmeyer
Wayne State University
Detroit, Michigan, USA
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
