Re: strange behavior of bash

2005-09-21 Thread Yitzchak Scott-Thoennes
On Wed, Sep 21, 2005 at 06:52:08AM -0600, Eric Blake wrote: > I'm not familiar with DOS promote. Is it some other vendor's shell? Does > it provide its own bash in your home directory, which could explain why > you get a different behavior depending on what directory you are in when > you try to

Re: strange behavior of bash

2005-09-21 Thread faif cn
Thank you very much all for your replies. I think I should clarify somthing first. Windows has two places to set path parameters "Local Machine" and "User environment", what I changed is "local machine" one which means it affects anyone use this pc. 1. I do have /cygwin/bin in my "User environment

RE: strange behavior of bash

2005-09-21 Thread Dave Korn
Original Message >From: faif cn >Sent: 21 September 2005 10:04 > Thank you Dave > > On 9/20/05, Dave Korn wrote: >>> >>> I deleted some values in Windows Local Environment variable "PATH". >>> My original "HOME" is c:/home/myname/. And then: >> >> it broke. So put them back! >

Re: strange behavior of bash

2005-09-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 9/21/2005 7:14 AM: >>Your cygcheck was hard to read, as it was not a plain-text attachment >>(hmm, maybe we could update the problem-reporting instructions to tell >>people to create cygcheck.txt instead of cygcheck.o

Re: strange behavior of bash

2005-09-21 Thread Christopher Faylor
On Wed, Sep 21, 2005 at 06:52:08AM -0600, Eric Blake wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >According to faif cn on 9/21/2005 3:04 AM: >> >> What I deleted is "borland c" bin directory to avoid cygwin confusing >> two "make" tools. and maybe some other PATH variables which I bel

Re: strange behavior of bash

2005-09-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to faif cn on 9/21/2005 3:04 AM: > > What I deleted is "borland c" bin directory to avoid cygwin confusing > two "make" tools. and maybe some other PATH variables which I believe > set by some outdated software. It left as Your cygcheck was

Re: strange behavior of bash

2005-09-21 Thread Larry Hall
At 05:04 AM 9/21/2005, you wrote: >Thank you Dave > >On 9/20/05, Dave Korn korn artimi com> wrote: > ^^^ This is important if you want people to reply to you. >> > I deleted some values in

Re: strange behavior of bash

2005-09-21 Thread faif cn
Thank you Dave On 9/20/05, Dave Korn <[EMAIL PROTECTED]> wrote: > > > > I deleted some values in Windows Local Environment variable "PATH". > > My original "HOME" is c:/home/myname/. And then: > > it broke. So put them back! What I deleted is "borland c" bin directory to avoid cygwin co

RE: strange behavior of bash

2005-09-20 Thread Dave Korn
Original Message >From: faif cn >Sent: 20 September 2005 17:26 > Hello all, > > I deleted some values in Windows Local Environment variable "PATH". > My original "HOME" is c:/home/myname/. And then: it broke. So put them back! If that doesn't fix it, -> http://cygwin.com/prob