X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.4 required=5.0	tests=AWL,BAYES_50,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Date: Wed, 18 Aug 2010 14:49:11 -0500
From: Brian Ford <Brian.Ford@FlightSafety.com>
Reply-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Re: "run" changes behavior with cygwin-17.6
In-Reply-To: <20100818193446.GC11340@calimero.vinschen.de>
Message-ID: <Pine.CYG.4.58.1008181447060.4004@PC1163-8460-XP.flightsafety.com>
References: <380-220108318145158645@cantv.net> <20100818150920.GY11340@calimero.vinschen.de> <4C6C1490.3040202@cwilson.fastmail.fm> <4C6C1582.1080801@acm.org> <20100818182412.GA22698@ednor.casa.cgf.cx> <AANLkTikBTgg9M=xuZ4S2VkNU+Zr=hy3C=_Tr8BPj5baD@mail.gmail.com> <20100818185421.GC22698@ednor.casa.cgf.cx> <20100818191340.GB11340@calimero.vinschen.de> <20100818191906.GD22698@ednor.casa.cgf.cx> <20100818192238.GA27567@ednor.casa.cgf.cx> <20100818193446.GC11340@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Wed, 18 Aug 2010, Corinna Vinschen wrote:

> On Aug 18 15:22, Christopher Faylor wrote:
> > On Wed, Aug 18, 2010 at 03:19:06PM -0400, Christopher Faylor wrote:
> > >>already does for the environment.  Dropping the environment had roughly
> > >>the same consequences way back when, after all.
> > >
> > >Except that not every program uses the windows environment.  This affects
> > >quite a few native windows calls.
>
> It affects every program which calls CreateProcess or ShellExecute, for
> instance.  This includes GDB, tcl, run, run2, cygstart, etc.
>
> > And, for that reason, I think we should reconsider this change.  Maybe
> > as a compromise maybe we could at least avoid cd'ing to the dummy
> > location on entry to the first cygwin program.
>
> I disagree.  When do you change the directory to //?/pipe then?  The
> first time chdir is called?

Can someone please remind me why you shouldn't change to that directory
only when SetCurrentDirectory would fail due to a long path, virtual
path, etc?  I think it was covered in the developer list, but I can't find
it right now.

-- 
Brian Ford
Staff Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained crew...

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

