RE: PATHs in Windows and Cygwin

2006-06-13 Thread Charli Li
TED] Behalf > Of Christopher Faylor > Sent: Tuesday, June 13, 2006 6:48 PM > To: cygwin@cygwin.com > Subject: Re: PATHs in Windows and Cygwin > > > On Tue, Jun 13, 2006 at 06:24:43PM -0400, Charli Li wrote: > >You have to set yourself up with a Windows batch script befor

Re: PATHs in Windows and Cygwin

2006-06-13 Thread Christopher Faylor
On Tue, Jun 13, 2006 at 06:24:43PM -0400, Charli Li wrote: >You have to set yourself up with a Windows batch script before you can even >start GNU programs. No. You don't. You just need to have, e.g., c:\cygwin\bin in your PATH, as Dave said. I'm not sure why you thought you needed to elaborate

RE: PATHs in Windows and Cygwin

2006-06-13 Thread Charli Li
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Dave Korn > Sent: Tuesday, June 13, 2006 5:39 AM > To: cygwin@cygwin.com > Subject: RE: PATHs in Windows and Cygwin > > > On 13 June 2006 08:18, fergus wrote: > > > However, if I start Cygwin from a command prompt

RE: PATHs in Windows and Cygwin

2006-06-13 Thread Dave Korn
On 13 June 2006 08:18, fergus wrote: > However, if I start Cygwin from a command prompt having first set the > Windows PATH to (null) as follows > > c:> set PATH= > c:> j:\bin\bash > > then not everything works: I get messages of the style "This application has > failed to start because

PATHs in Windows and Cygwin

2006-06-13 Thread fergus
My Windows PATH (XP Pro) is the moderately standard %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem None of this is inherited when I use Cygwin, where the PATH is set to be /home/fergus/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin:/bin However, if I start Cygwin from a comma