Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<80575AFA5F0DD31197CE00805F650D7602CFD4@wilber.adroit.com>
From:	"Robinow, David" <drobinow AT dayton DOT adroit DOT com>
To:	cygwin AT cygwin DOT com
Subject:	RE: competition for HOME environment variable
Date:	Thu, 23 Aug 2001 09:34:18 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)

> From: Jean-Philippe Grivet [mailto:grivet AT cnrs-orleans DOT fr]
> Subject: competition for HOME environment variable
> ...
> I have tested cygwin software in a very limited fashion (vim and gcc,
> mostly) and find that they perform satisfactorily.

 GOOD!
> 
> My guess is that cygwin, Astex, and Scilab (all ports of 
> Linux programs)
> require HOME environment variable.
> This was  previously defined in order to use a WIN port of Emacs along
> with Astex.
> 
> This seems to be confirmed by the cygcheck file which is 
> appended. This
> file also contains unwanted references to Borland C directory 
> and files.
> 
> So my question is: how can I resolve this conflict betwen two programs
> that use the same environment variable ?
 What's there to resolve?  Your system seems to be running properly.
Are you having some difficulty not mentioned in your post?

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

- Raw text -