Re: "run" changes behavior with cygwin-17.6

[Charles Wilson <cygwin at cwilson dot fastmail dot fm>]

On 8/19/2010 6:48 AM, Corinna Vinschen wrote:
> I applied the patch which adds the CW_SYNC_WINCWD code and I updated
> the documentation accordingly.
> 
> I uploaded the rewritten chapter about using the Win32 file API here:
> 
>   http://cygwin.de/cygwin-ug-177/using.html#pathnames-win32-api
> 
> Please have a look.

The commentary about the errno values is duplicated. Other than that, it
seems clear.  I have one question, specifically as it relates to
run/run2/cygstart: these apps use CreateProcess.  In the documentation,
you say:

> If you need a valid Win32 CWD only for a child application started
> via CreateProcess and friends, you don't have to set your own Win32
> CWD. In that case, just utilize the lpCurrentDirectory parameter. See
> the description of the CreateProcess  function in the MSDN manual
> pages.

But earlier in this thread, you suggested that run/run2/cygstart should
use the new CW_SYNC_WINENV.  Which is it?

> As for the documentation about CW_SYNC_WINENV, it's already in the
> "official" docs at
> 
>   http://cygwin.com/cygwin-ug-net/setup-env.html#setup-env-win32

Thanks.

--
Chuck

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