"run" changes behavior with cygwin-17.6

Corinna Vinschen corinna-cygwin@cygwin.com
Thu Aug 19 14:00:00 GMT 2010

On Aug 19 09:20, Charles Wilson wrote:
> 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

Oh, fixed.  I missed to upload the latest version of the file.  Sorry!
(I experimented with DocBook's segmentedlists and tables)

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

It's something completely different.

CW_SYNC_WINCWD is to sync the CWD.  But it's your choice, whether
you use CW_SYNC_WINCWD or just utilize the lpCurrentDirectory param
to CreateProcess.

> >   http://cygwin.com/cygwin-ug-net/setup-env.html#setup-env-win32
> Thanks.

CW_SYNC_WINENV is for sync'ing the Win32 *environment* with the Cygwin


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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