Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 9 Oct 2001 13:36:55 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Ignore the CYGWIN environment variable if child of a cygwin process?
Message-ID: <20011009133655.A25333@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.21i

I keep seeing people who have set the CYGWIN environment variable from the bash
shell.  This causes strange problems.

I wonder if it would be worthwhile to ignore the CYGWIN environment variable
if it is set in a process that is a child of a cygwin process.

The downside is that there are probably some situations where it
actually works ok to do this and that we'll end up screwing up people
who know what they're doing.

We could just issue a warning but I hate for cygwin to be noisy in these kinds
of situations.

Any thoughts?

cgf