Installing new versions of vim doesn't uninstall old versions

Christopher Faylor
Fri Nov 12 05:46:00 GMT 2010

On Thu, Nov 11, 2010 at 04:18:06PM -0500, Larry Hall (Cygwin) wrote:
>On 11/11/2010 3:29 PM, Christopher Faylor wrote:
>> On Thu, Nov 11, 2010 at 01:57:57PM -0500, Larry Hall (Cygwin) wrote:
>>> On 11/11/2010 1:45 PM, Ren?? Berber wrote:
>>>> On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote:
>>>>> On 11/11/2010 1:07 PM, Harrington, John wrote:
>>>>>> I recently had a problem with vim that was the result of my unwittingly
>>>>>> having two previous versions of vim in my /usr/bin.  Is it normal for the
>>>>>> cygwin installer not to delete or clobber the previous versions?  I'm not
>>>>>> sure what I did wrong, if anything, in updating my cygwin installation.
>>>>> Probably just a local glitch.  We haven't seen other reports of this,
>>>>> though
>>>>> that could just mean that no one else has noticed.
>>>> Actually there are many reports, its not just vim, similar reports have
>>>> been made about ssh, and checking for un-installed updates showed other
>>>> cases.
>>>> setup.exe just leaves<you-name-it> (or and the change
>>>> never happens.
>>>> It may have been one of the old versions of setup, I don't know, some
>>>> upgrades do happen correctly when an old one is still there, and left there.
>>> Yeah, maybe that explains this one too.  If John was using 'vim.exe' when he
>>> did an update, then this could be the result.  But there is no vim-specific
>>> issue here.
>> And, of course, if anyone can provide a clearly-failing test case we'll fix
>> the problem in setup.exe.
>But this would make any existing work-arounds obsolete.  I think we need to
>consider issues of backward bug compatibility before we blindly go fixing
>'setup.exe'. ;-)

Sorry.  You're right.

You're very wise.  You should start blog.


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list