Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: Cygwin 1.3.19 Windows 2000 Professional SP3 bash $home /usr/bin/%USERPROFILE% Date: Sun, 26 Jan 2003 16:20:04 -0500 Message-ID: <83040F98B407E6428FEC18AC720F5D73E501B3@exchange.tropicnetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rolf Campbell" To: "cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h0QLKFC31334 > -----Original Message----- > From: Larry Hall (RFK Partners, Inc) [mailto:lhall AT rfk DOT com] > Sent: Sunday, January 26, 2003 4:03 PM > To: Elfyn McBratney; cygwin; David Christensen > Subject: Re: Cygwin 1.3.19 Windows 2000 Professional SP3 bash > $home /usr/bin/%USERPROFILE% > ... > > environments between two products. While solutions for > somehow automating the detection of this clash and resolving > it in the > Cygwin installer (setup) is, no doubt, possible, it's pretty > far-fetched to claim this is a Cygwin issue. I agree that this isn't a cygwin problem, but it might be nice if setup announced that HOME is being set to something that will screw up cygwin. -Rolf -- 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/