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: <3DA4260E.3070909@etr-usa.com> Date: Wed, 09 Oct 2002 06:50:22 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cygwin-L Subject: Re: Apparent bug with vim References: <12B638FEE763F74696D8544752E7204812D17B AT bgsmsx101 DOT iind DOT intel DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam. Abhishek, Dev wrote: > > Problem description: When a file with extension ".con" is opened with vim, > it produces an error message such as the following. In /usr/share/vim/vim61/filetype.vim, find the "Century Term Command Scripts" line and comment it out. That will probably fix the problem. This isn't a bug, per se, it's that vim comes preconfigured to do special things with .con files. Since your .con files aren't Century Term command scripts, vim is barfing on the data in them when it loads them. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/