Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <004401c2c58e$064f1870$0b01a8c0@w2k30g>
From: "David Christensen" <dpchrist AT holgerdanske DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Fw: Cygwin 1.3.19 Windows 2000 Professional SP3 bash $home   /usr/bin/%USERPROFILE%
Date: Sun, 26 Jan 2003 14:55:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

cygwin AT cygwin DOT com:

Larry Hall wrote January 26, 2003 1:44 PM:
> there's an implication in all this that setting HOME breaks bash or
> Cygwin.

I infer from the above that the default Windows setting for HOME is no
setting at all?  e.g. the variable is undefined?


Testing the above hypothesis by deleting my Windows HOME environment
variable -- Bash/Cygwin now starts in the correct directory
(/home/dpchrist) and the Bash environment variable HOME is properly set!


I also see two more Windows variables:

    TEMP    %USERPROFILE%\Local Settings\Temp

    TMP     %USERPROFILE%\Local Settings\Temp

I'll assume Dia Win32 Installer created those and blow them away as
well.


I now agree that Dia Win32 Installer was the source of my Bash/Cygwin
problems.  Shame on Dia Win32 Installer for breaking Cygwin, and shame
on Dia Win32 Installer for not returning my system to it's previous
state when uninstalled.  I will be sure to thank those people for the
grief they have cause me and the wasted bandwidth they have caused on
this mailing list.


So, to summarize:

    Bash/Cygwin was broken because the Dia Win32 Installer sets the
    Windows HOME environment variable when Bash/Cygwin expects it not to
    be set at all (e.g. unset).


However, I still say there is a Bash/Cygwin bug -- if Bash/Cygwin reads
the Windows HOME environment variable and gets "%USERPROFILE%", it
should evaluate that to get "C:\Documents and Settings\dpchrist" and set
my home directory to "/cygdrive/c/Documents and Settings/dpchrist".
Starting in, and setting HOME to, "/usr/bin/%USERPROFILE%" is bad.


David Christensen
dpchrist AT holgerdanske DOT com


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/