X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 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: <4C6C1582.1080801@acm.org> 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> Date: Wed, 18 Aug 2010 19:25:56 +0100 Message-ID: Subject: Re: "run" changes behavior with cygwin-17.6 From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 18 August 2010 18:16, David Rothenberger wrote: > On 8/18/2010 10:12 AM, Charles Wilson wrote: >> On 8/18/2010 11:09 AM, Corinna Vinschen wrote: >>> Looks like the "run" tool now needs a call to >>> >>> =C2=A0 =C2=A0CYGWIN_CONV_TO_POSIX_PATH ((get_cwd (), win32_cwd)); >>> >>> and then use win32_cwd in the call to CreateProcess. >>> >>> See http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32-api >> >> Yep. run2 also needs a similar update. >> >> Thanks for the heads up; I didn't really think about how the recent >> changes to cygwin's cwd handling would affect those two packages. > > 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. Ouch. This might affect even more cygutils. We really should have thought of that. At least there aren't any chdir() calls in any of the cygutils, so it should primarily be a question of setting the Win32 current directory in line with the POSIX one at startup, in any of the utils that may invoke a Win32 function with a relative path. Chuck, do you need a hand with going through them? 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