X-Spam-Check-By:	sourceware.org
Message-ID:	<4495CA35.2020804@tlinx.org>
Date:	Sun, 18 Jun 2006 14:48:37 -0700
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: vim-7.0.017-1
References:	<announce DOT 20060612112311 DOT GA19412 AT calimero DOT vinschen DOT de>
In-Reply-To:	<announce.20060612112311.GA19412@calimero.vinschen.de>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Corinna Vinschen wrote:
> I have updated the version of vim on cygwin.com to 7.0.017-1.
>
> This is the long awaited vim 7.0, latest patchlevel 17.  Cygwin Vim
> still builds from the vanilla sources.
>   
---
    Vim 7 seems to still have a few kinks to work out and doesn't
seem nearly as stable as vim64.  Since vim7 is already out as vim,
maybe vim6.4 could be made available as a separete vim6 or vim64
package for those not wanting to be on the bleeding edge?  Some
important features have stopped working in 7, and judging from the
mailing list, there seems to be a large uptick in problems in 7.

    Either that, or maybe (I'd think more hassle, but...) roll
vim-current back to 6.4 and leave vim7 as a future release until
vim7 hits 7.1 or so?

Or is waiting for a stable version too passé? :-)

linda





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -