On 11 August 2010 20:55, John Carey wrote: > On Aug 11 01:49 Corinna Vinschen wrote: >> there's no Win32-safe way to set a new >> directory handle as cwd in Vista and later anymore. Since there's no >> official API to set the cwd using a directory handle, there's no way to >> set the Win32 cwd to a directory with restricted permissions. >> This *is* frustrating. >> >> I'll look into another solution. Probably we will have to call >> SetCurrentDirectory again and ignore any error. I don't accept the >> aforementioned restriction for POSIX calls. > > So is your idea that if SetCurrentDirectory() fails because > of path length or permissions, then Cygwin would just accept > the failure and keep an internal record the > POSIX current working directory and use that for all > Cygwin calls, not the Win32 notion of current directory?
Yes. The question then becomes what to do about the Win32 working directory in that case. 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
