Cygwin CWD vs. Win32 CWD (was Re: [ANNOUNCEMENT] Updated: vim-7.3.003-1)

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Wed Aug 25 14:21:00 GMT 2010


On Wed, Aug 25, 2010 at 04:17:46PM +0200, Corinna Vinschen wrote:
>On Aug 25 09:44, Christopher Faylor wrote:
>> On Wed, Aug 25, 2010 at 01:46:13PM +0200, Corinna Vinschen wrote:
>> >On Aug 20 22:31, Corinna Vinschen wrote:
>> >> On Aug 20 16:03, Christopher Faylor wrote:
>> >> > On Fri, Aug 20, 2010 at 09:27:25PM +0200, Corinna Vinschen wrote:
>> >> > >Erm... btw., how is that different from the message, if you need a
>> >> > >valid Win32 CWD in your hybrid app, use cygwin_internal(CW_SYNC_WINCWD)?
>> >> > 
>> >> > My supposition is that the breakage for hybrid applications is much more
>> >> > pervasive than for programs which want to delete directories that someone
>> >> > has cd'ed to.
>> >> > 
>> >> > But, actually, I am liking the "just relink your app like this if that
>> >> > is what you want" solution better.  That means minor tweaks to the
>> >> > current Cygwin code.  A pure Cygwin app continues to behave like linux.
>> >> > You just have to rebuild your hybrid app.
>> >> > 
>> >> > I think I'll work on a proof-of-concept for that.
>> >> 
>> >> That sounds good.  [...]
>> >
>> >I have created a patch which implements both, a /usr/lib/winsynccwd.o
>> >which you can link against, and a new environment setting CYGWIN=winsynccwd.
>> 
>> Uh.  I said *I* was doing this.  You even quoted me above.  Why didn't
>> you at least *ask* me about this?
>
>Sorry about that.  I had a bit of time and thought it would be helpful
>to move this issue forward.  Feel free to disregard the actual code.

I had code ready to check in but I was actually waiting to see where the
discussion went before bothering.

cgf



More information about the Cygwin-developers mailing list