X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100818193940.GA4358@ednor.casa.cgf.cx> References: <20100818150920.GY11340@calimero.vinschen.de> <4C6C1490.3040202@cwilson.fastmail.fm> <4C6C1582.1080801@acm.org> <20100818182412.GA22698@ednor.casa.cgf.cx> <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> <20100818193940.GA4358@ednor.casa.cgf.cx> Date: Wed, 18 Aug 2010 20:47:37 +0100 Message-ID: Subject: Re: "run" changes behavior with cygwin-17.6 From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 18 August 2010 20:39, Christopher Faylor wrote: > On Wed, Aug 18, 2010 at 09:34:46PM +0200, 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. =C2=A0Dropping the environment had = roughly >>> >>the same consequences way back when, after all. >>> > >>> >Except that not every program uses the windows environment. =C2=A0This= affects >>> >quite a few native windows calls. >> >>It affects every program which calls CreateProcess or ShellExecute, for >>instance. =C2=A0This includes GDB, tcl, run, run2, cygstart, etc. > > And, the current change affects every one of those programs and more. Right, that's a pretty big argument for favouring Windows integration rather than Linux compatibility here. So what would be the consequences of not allowing the current working directory of a running process to be deleted? >>> And, for that reason, I think we should reconsider this change. =C2=A0M= aybe >>> as a compromise maybe we could at least avoid cd'ing to the dummy >>> location on entry to the first cygwin program. >> >>I disagree. =C2=A0When do you change the directory to //?/pipe then? =C2= =A0The >>first time chdir is called? > > Yes. I'm not convinced such a compromise would be worthwhile, because it would forfeit Linux compatibility while still breaking some Win32-using programs. I think it should be one way or the other: either stick with the current approach, or always sync the Win32 working directory up-to-date (except when that's not possible). Andy -- 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