Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Thu, 23 Dec 2004 09:37:44 -0800
From: George <d1945@sbcglobal.net>
To: cygwin@cygwin.com
Subject: Setting $HOME for Windows
Message-ID: <20041223173744.GA752@home>
Reply-To: George <d1945@sbcglobal.net>
Mail-Followup-To: cygwin@cygwin.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

I remember reading some time ago a vague admonition against manually
setting $HOME as a Windows environment variable.  

I can't seem to find the message, so if someone can elaborate on why
this is A Bad Thing, I'd appreciate it.  This is for those of us
pursuing the Holy Grail of integrating Cygwin with Windows (or,
depending on one's view, Windows with Cygwin), and doing our best to
ignore the less-than-holy %USERPROFILE% construct.

--
George


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