This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ANNOUNCEMENT] Updated: vim-7.3.003-1


2010/8/20 Christopher Faylor:
> On Fri, Aug 20, 2010 at 08:35:06PM +0200, Corinna Vinschen wrote:
>>On Aug 20 11:39, Christopher Faylor wrote:
>>> On Fri, Aug 20, 2010 at 05:09:20PM +0200, Thorsten Kampe wrote:
>>> >* Corinna Vinschen (Fri, 20 Aug 2010 16:33:17 +0200)
>>> >> Not weird at all. ?I could track this down to a point in Cygwin where
>>> >> it neglects to close a handle to a symlink when instructed to follow
>>> >> symlinks to their target. ?I checked in a patch. ?Please test the DLL
>>> >> I uploaded at
>>> >>
>>> >> ? http://cygwin.de/cygwin-ug-177/newer-cygwin1.dll.bz2
>>> >> ? (md5sum compressed ? 5eab6680538279206bf23c54244825d2)
>>> >> ? (md5sum uncompressed e4833a601edad1571a9c6e0352a8e381)
>>> >>
>>> >> which contains the fix. ?This should not leave the stray handles to
>>> >> vi, vim, etc in zsh. ?And the side-effect should be that setup.exe
>>> >> does not complain anymore in the original scenario.
>>> >
>>> >Yes, the evil handles are gone.
>>>
>>> Sounds like a reason for a new cygwin release.
>>
>>Definitely. ?I was planning to release 1.7.7 this weekend or early
>>next week.
>>
>>> Did we ever come to a consensus on what to do with the Cygwin cwd stuff?
>>> It sounded like people were reluctantly agreeing with my reluctant
>>> proposal to not set the windows cwd to the pipe pseudo-location unless
>>> chdir was explicitly called.
>>
>>I'm not really convinced that this is a good solution. ?It is somewhat
>>half-half, sticking to Win32 backward compatibility but not quite. ?This
>>hits Cygwin applications in the back in the first place. ?How many POSIX
>>tools actually call chdir? ?Most shells, but otherwise?
>
> I can't believe that I'm arguing for the Windows API but to counter the
> argument: How many POSIX applications are confused by the inability to
> delete the current directory? ?I like that Cygwin allows you to do this
> now but I'm wondering how much pain we'll be giving to previously
> working hybrid Cygwin applications.

I had this case only once in a perl module, svn-bisect if I remember
correctly and the maintainer quickly adjusted his linuxism to be more
friendly to other platforms. i.e. working around rm `pwd` was not an
issue at all.
-- 
Reini Urban


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]