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 X-Apparently-From: Message-ID: <3BC338F3.3FDF0FE9@yahoo.com> Date: Tue, 09 Oct 2001 13:50:43 -0400 From: Earnie Boyd Reply-To: CD List X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin-developers AT Cygwin DOT Com Subject: Re: Ignore the CYGWIN environment variable if child of a cygwin process? References: <20011009133655 DOT A25333 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com