Date: Wed, 18 Aug 2010 14:24:12 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: "run" changes behavior with cygwin-17.6
Message-ID: <20100818182412.GA22698@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <380-220108318145158645@cantv.net> <20100818150920.GY11340@calimero.vinschen.de> <4C6C1490.3040202@cwilson.fastmail.fm> <4C6C1582.1080801@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C6C1582.1080801@acm.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Wed, Aug 18, 2010 at 10:16:50AM -0700, 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
>>>
>>>    CYGWIN_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.

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"?

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