DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=rCv2kUMiNv3jmTZqzpO4Qjy9PMpaN8feAbEo/rGv4kv
	dTT6wtt+raPnOzUZM6Y2Opi1WU6YsnqJaDRCEZzYs228rqJ2Z0dexqspY1D4Z7Mm
	zeePeVN/Gi+wrSuGDYdYYI2b9Yhyefvvy+PlB4Z1iAdpdrtePWTSj8JfzCo9Fl7c
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CAKChYSq8RTRpH3OprWSHKqWbT9POjHGmcMGRESqb+KXmVmecCQ@mail.gmail.com>
References: <52096B42.8010702@Kautler.net> <CAKChYSpP=AKMOc7yHL9NMJyQeKEvsswgKFTyJVKZZrg5vqbPsQ@mail.gmail.com> <CAKChYSpBEmXquHxkC2LZSmgH60kXfTxriDVX_Ap6HC4GNMRWMg@mail.gmail.com> <20131206171721.GA7240@ednor.casa.cgf.cx> <CAKChYSqyXHXUh1GVNsOEZWPbS=RsObb_gOCLX5kycMFWej-mwQ@mail.gmail.com> <20131206234833.GC3154@phoenix> <CAKChYSrNhmza5TBZNQQnaAC2LKJz7G1MbJi-+1K97c=Z0h9CJQ@mail.gmail.com> <CAKf2h5S8n+JX1LVbf+ZZDRUneJuiG0OQ9B9wTpr3WVj2gUkNSg@mail.gmail.com> <CAKChYSrsuLrO=OxZqD7wSeti8-oGtZeYr5yy3rjxxQGU6zzuxg@mail.gmail.com> <CAKf2h5S+b8kjuXm2bmuEwUGk9bLfJjq602-e_YYGhcptKd_XWQ@mail.gmail.com> <20131209125119.GJ2527@calimero.vinschen.de> <CAKChYSq8RTRpH3OprWSHKqWbT9POjHGmcMGRESqb+KXmVmecCQ@mail.gmail.com>
From: Frank Fesevur <ffes@users.sourceforge.net>
Date: Mon, 9 Dec 2013 15:06:18 +0100
Message-ID: <CAKf2h5SNP3zck69kmA6NbPv6EdakMtnu=zbiviDu6fZ4DmW1iw@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

2013/12/9 Björn Kautler:
> Again, what I talk about is NOT an issue of vi vs. vim.
> What I talk about is a breaking change in vim that was introduced
> while doing a change for vi.
> But it is NOT an issue of vi vs. vim.

That patch was introduced when people started to complain that they
got errors about commands not recognized in their vimrc. The root
cause of this was obviously the whole vi != vim thing.

I always use ~/.vimrc so I never ran into your problem.

Regards,
Frank

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