This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: strange behavior of bash
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 21 Sep 2005 15:13:06 +0100
- Subject: RE: strange behavior of bash
----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!
>
> 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
>
>
"%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\matlab6p5\
bin\win32;C:\PROGRA~1\ULTRAE~1;%HTC_PIC%\BIN;;C:\Program
> Files\Common Files\GTK\2.0\bin\"
Get rid of that double-semicolon between %HTC_PIC%\BIN and the GTK path.
> There is nothing special, the same PC with same path variables run
> cygwin no problem. I just get confused why this behavior happens, and
> with invoke --login parameter.
Meaning this behaviour ?
>> If I type "bash" in any other directories, the bash promote can be
>> shown successfully and I can use bash environment.
>>
>> If I type "bash" in my home directory, it just hangs for seconds and
>> back to dos promote and nothing happened. Alternatively "bash --login"
>> has same behavior.
You must have a file called bash in your home directory, and that empty
component between the two double-semicolons counts as adding '.' to your
$PATH in POSIX.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/