Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 14:17:54 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT Com Subject: Re: Ignore the cygwin environment variable if child of a cygwin process? Message-ID: <20011009141754.C25375@redhat.com> Reply-To: cygwin-developers AT cygwin DOT Com Mail-Followup-To: cygwin-developers AT cygwin DOT Com References: <20011009133655 DOT A25333 AT redhat DOT com> <3BC338F3 DOT 3FDF0FE9 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BC338F3.3FDF0FE9@yahoo.com> User-Agent: Mutt/1.3.21i On Tue, Oct 09, 2001 at 01:50:43PM -0400, Earnie Boyd wrote: >Christopher Faylor wrote: >> >> 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? >> > >Hmm... Is it just the parent process or the first process (i.e.: dll >initialization) you want to target? I've always suggested stopping all >processes when wanting to change the CYGWIN variable. Just the parent process. It should be ok to set CYGWIN to different values in different windows. Stopping all processes *is* a good idea, though, when instructing people who are unknowledgeable about cygwin. cgf