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
Date: Mon, 16 Jun 2003 12:59:48 -0700
From: Brian Koehmstedt <bpk AT hungry DOT com>
To: cygwin AT cygwin DOT com
Subject: win32 dia and HOME=/usr/bin/%USERPROFILE% fix
Message-ID: <20030616125948.A19258@hungry.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
User-Agent: Mutt/1.3.23i


I had the problem of bash starting up with the home directory being
/usr/bin/%USERPROFILE%.

I searched the mailing list and came up with a January thread on the issue,
which informed me that the problem was due to the win32 dia installer
creating a Windows environment HOME variable that superceded bash's normal
HOME.

(the start of the Jan thread is at
http://sources.redhat.com/ml/cygwin/2003-01/msg01503.html)

In that thread I saw some suggestions on editing /etc/profile to fix it, but
I found this to be an easier all-around solution:

Edit the cygwin.bat file and put "set HOME=" somewhere in it.  This unsets
the Windows HOME environment variable and Cygwin/bash starts up with the
correct HOME environment variable.

I use startxwin.sh to start up X, but if you use startxwin.bat then you
probably have to edit that file too since it's another Windows batch file
that starts up bash shells.

-- 
Brian Koehmstedt
bpk AT hungry DOT com

--
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/