Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Shankar Unni Subject: vim can't handle DOS line endings in .vimrc (was Re: [ANNOUNCEMENT] Updated: vim-6.1.300-1) Date: Sun, 09 Feb 2003 14:25:39 -0800 Lines: 29 Message-ID: <3E46D563.8040301@cotagesoft.com> References: <20030209175012.CBD5A1B8E8@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en Corinna Vinschen wrote: > I've updated the version of vim to 6.1.300-1. I've just updated to the latest everything (cygwin 1.3.20, vim 6.1.300-1). I normally leave the CYGWIN env var undefined (i.e. cygwin defaults). Vim now complains about my .vimrc file (which has DOS line endings). CYGWIN settings (I tried various settings with "tty" and "notty") make no difference. Each line gets a complaint about the ^M: Error detected while processing /cygdrive/c/Shankar/.vimrc: line 1: Trailing characters: nocompatible^M line 2: Invalid argument: background=dark^M line 4: Invalid argument: xterm^M line 5: Invalid argument: selectmode=mouse^M and so on. Something broken in vim, or was the build different somehow? Rolling back to 6.1.2 fixes this problem. -- Shankar. -- 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/