Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3500515B75D9D311948800508BA37955014BDA87@EX-LONDON> From: Vince Hoffman To: "'cygwin AT cygwin DOT com'" Subject: RE: Cygwin survey: Next vim version with perl support? Date: Wed, 30 Apr 2003 11:19:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" > > Well... when writing my survey mail I was actually mulling over an > additional sentence like "Note that I'll maintain only one package." > but dropped it for the final mail. I should have known better. > > The problem with vim is the number of configure options which do make > different sense for different people. What should I do? > > - pure vim > - perl support > - python support > - tcl support > - ruby support > - perl and python but not tcl > - gvim with win32 interface (actually unsupported under Cygwin) > - gvim with X interface > - Which X interface, gtk, gnome, motif, athena? > - ... > > See what I mean? You'd never hit the right combination. I've just > checked the vim release on my Linux box and found out that it's also > not built with any of the interpreter language support. Of course > I'm using my own handcrafted build of vim... > > > Corinna > Corrinna, Sorry about that. I regretted the suggestion as soon as I suggested it as it should be easy enough to build your own vim if you require more advanced features, and you're already doing plenty without creating another package. I think I'd change my vote to no on second thoughts since installing perl just to use vi is a little over the top. Vince -- 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/