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 To: cygwin AT cygwin DOT com Subject: Re: Cygwin survey: Next vim version with perl support? References: <20030430083411 DOT GR19711 AT cygbert DOT vinschen DOT de> <20030430094847 DOT GE52453 AT justpickone DOT org> <20030430100121 DOT GV19711 AT cygbert DOT vinschen DOT de> <871xzkkxqs DOT fsf AT peder DOT flower> <20030430115812 DOT GY19711 AT cygbert DOT vinschen DOT de> Organization: Jan at Appel Mail-Followup-To: cygwin AT cygwin DOT com From: Jan Nieuwenhuizen Date: 30 Apr 2003 14:19:14 +0200 In-Reply-To: <20030430115812.GY19711@cygbert.vinschen.de> Message-ID: <87llxsjhz1.fsf@peder.flower> Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Corinna Vinschen writes: > Apparently we're using different Linuces ;-) Oh no, how did that happen? Fragmentation BAD. Single vendor GOOD. :-) I Forgot to vote, btw: [ ] Yes, please add perl support to the next Cygwin vim release. [X] No, go away with that [ ] What's vim? ... at least until there's an(other/dditional) lightweight VI package. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- 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/