From: dumser AT ti DOT com (James Dumser) Subject: Re: HOME and bash 27 Jan 1997 16:05:01 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <199701271401.IAA20744.cygnus.gnu-win32@lesol1.dseg.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Original-To: ron AT OrCAD DOT com (Ron Forrester) Original-Cc: gnu-win32 AT cygnus DOT com In-Reply-To: <32E8D370.7409@netrix.com> from "Long Doan" at Jan 24, 97 10:21:20 am X-MIMI-Options: headers none X-Mailer: ELM [version 2.4 PL23] Content-Length: 1095 Original-Sender: owner-gnu-win32 AT cygnus DOT com On Fri, 24 Jan 1997 10:21:20 -0500, Long Doan wrote: >I have a setup similar to yours, so maybe this will help. I set the HOME >variable via the control panel, like HOME=/home/ld, and in my emacs.bat >(NTEmacs's startup file) I set HOME=%HOMEDRIVE%%HOMEPATH%, which is >D:\home\ld. If you want to invoke NTEmacs via some icon, just tell that >icon to invoke the .bat file. > >Ron Forrester wrote: >> I don't (anymore) define HOME in my .bashrc. I have a bash.cmd which I >> run to launch bash, which is: >> >> @echo off >> set HOME=/usr/rjf >> c:/usr/rjf/b17.1/h-i386-cygwin32/bin/bash.exe >> exit >> >> this has fixed that problem. The source of this problem appears to be that bash captures the value of HOME when it starts -- before it executes .profile/.bashrc -- and does not pay attention to later changes of the HOME variable (as far as ~ is concerned). Thus setting HOME in your .profile has no effect; ~ is still the pre-bash value of HOME. (cd without any arguments works correctly, using the current value of HOME.) -- James Dumser 972-462-5335 dumser AT ti DOT com - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".