"run" changes behavior with cygwin-17.6

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Wed Aug 18 18:24:00 GMT 2010

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


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

More information about the Cygwin mailing list