Re: bash incorrectly determines HOME and HOMEDRIVE

2004-03-26 Thread Ralf G. R. Bergs
Larry Hall wrote: [...] HOMEDRIVE is set by Windows. ACK. I was able to verify that. I'd agree. But moving profiles like you did is not likely to be without repercussions. I'm assuming that MS wouldn't recommend this. Nevertheless, Actually, it's not a problem at all. I used Windoze built-in

RE: bash incorrectly determines HOME and HOMEDRIVE

2004-03-25 Thread Ken Thompson
I don't think this is really a bash issue. I think HOMEDRIVE is actually set by XP and bash is just importing it. Cygwin has a default for NOME if it is not set but it is unlikely to be what you desire. Just set the environment variable HOMEDRIVE to 'H:' and it will do exactly what you wish.

Re: bash incorrectly determines HOME and HOMEDRIVE

2004-03-25 Thread Ralf G. R. Bergs
Ken Thompson wrote: I don't think this is really a bash issue. I think HOMEDRIVE is actually set by XP and bash is just importing it. Cygwin has a default for NOME if No. On my system, HOMEDRIVE was NOT set (neither for me personally, nor for all users.) it is not set but it is unlikely to be

RE: bash incorrectly determines HOME and HOMEDRIVE

2004-03-25 Thread Ken Thompson
-Original Message- Larry Hall Sent: Thursday, March 25, 2004 5:04 PM Subject: Re: bash incorrectly determines HOME and HOMEDRIVE Larry Hall WroteK HOMEDRIVE is set by Windows. You don't have to set it. And bash wouldn't know HOMEDRIVE from a hole in the wall

RE: bash incorrectly determines HOME and HOMEDRIVE

2004-03-25 Thread Larry Hall
At 05:14 PM 3/25/2004, you wrote: -Original Message- Larry Hall Sent: Thursday, March 25, 2004 5:04 PM Subject: Re: bash incorrectly determines HOME and HOMEDRIVE Larry Hall WroteK HOMEDRIVE is set by Windows. You don't have to set it. And bash wouldn't know HOMEDRIVE from