X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 18 Aug 2010 14:54:22 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "run" changes behavior with cygwin-17.6 Message-ID: <20100818185421.GC22698@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <380-220108318145158645 AT cantv DOT net> <20100818150920 DOT GY11340 AT calimero DOT vinschen DOT de> <4C6C1490 DOT 3040202 AT cwilson DOT fastmail DOT fm> <4C6C1582 DOT 1080801 AT acm DOT org> <20100818182412 DOT GA22698 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Aug 18, 2010 at 07:32:40PM +0100, Andy Koppe wrote: >On 18 August 2010 19:24, Christopher Faylor wrote: >>>I noticed a similar change in cygstart, too. I used to have a script >>>that would cd to a directory and then run cygstart. After the upgrade to >>>1.7.6, this stopped working. I had to use the --directory switch to >>>cygstart to get the right behavior. >> >> Call me dense but I don't understand why any changes are needed. ??If >> you're cd'ed to a non-Cygwin-special location why doesn't stuff "just >> work"? > >The Win32 working directory is changed to '\\?\PIPE\' at process >startup, otherwise the working directory can't be deleted from under >the process, which you can do on Linux. Yes, I guess I did not properly appreciate the fact that we presumably broke every CreateProcess call in a cygwin program when we did this. While I'm on record about not caring too much about that scenario, it seems meaner than usual for us to break this since the report which caused the recent change was from someone calling CreateProcess in a cygwin program. But, anyway, since we have broken this, I don't think we should force every user of CreateProcess to call CYGWIN_CONV_TO_POSIX_PATH. We probably should add an internal interface which sets the current working directory for windows if it can. cgf -- 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