X-Recipient: archive-cygwin AT delorie DOT com
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=ix1qZm/jsy5/HbTxaFvQBD7p/XFlbKdG8THqyH3Cfca
	d94LE/AQCd9COoElY7s/RTzivk/Cbyb1wcgrWir1QLBQxnTThQwVG0+boJYhdFcP
	PSMBANFG6B4Mr34gjmFdbHLOJh6sReQLPpr0+DxcpZ70okAyaJxZbaEk/xH6uu2M
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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;
	 s=default; bh=REAHe9w+q/Y3tDWCmZUDzitxeyk=; b=GHwRkRNN6pzP2D8PX
	sYgYqujcQgJxknjfHwzhaEX2NmBntFy4n1MYaFQgloS+/MRgoM9EsD/DfFTyaYLb
	Bt3qvMyxxwojcY5pgpV5zAkPMQ5gSzNjOzyvnLKS/JOqUmIehIzAgsSa9XltJCI6
	TjbCk4QRqdPmX21NTu8cMaddEo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: kautler.net
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=mime-version:in-reply-to:references:from:date:message-id:subject:to         :content-type:content-transfer-encoding;        bh=tWMqVaIDETvegcTJpUrSR2A4LyCMry8pweOOqzT/g6Y=;        b=lv3LlToP9JJkB3rEFoPdb3aTcvaXCK5aURCWOAzp3wkT1yDksOZyysTzsyYeQAgjiG         MuvSxkiT/FNh+RcRZa33wzzYCngNR8cep1eAgADPr8z1+Fj9JzNwAaMSRh3eMgdtlcL/         pIMTldgiiITsgaX0BJWFIpUthx20mLjWShywUn9k6CfiIj4pux8/btjK8uh34Ck2pC1a         5q766fBP1jtCTydvfP7w2sUXPpAiyS6tyXH9tJJ8g8HLxhrjfXUBH0RTKAlyuYF2CAOG         KbqGFLb/ASmTl3HXkQcL58cJNKZIaWWiVaaskTe5R1FQx0FF6L+zoV3CT/n+7vFPGc19         MXCg==
X-Received: by 10.49.116.141 with SMTP id jw13mr33627032qeb.2.1386598465298; Mon, 09 Dec 2013 06:14:25 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <CAKf2h5SNP3zck69kmA6NbPv6EdakMtnu=zbiviDu6fZ4DmW1iw@mail.gmail.com>
References: <52096B42 DOT 8010702 AT Kautler DOT net> <CAKChYSpP=AKMOc7yHL9NMJyQeKEvsswgKFTyJVKZZrg5vqbPsQ AT mail DOT gmail DOT com> <CAKChYSpBEmXquHxkC2LZSmgH60kXfTxriDVX_Ap6HC4GNMRWMg AT mail DOT gmail DOT com> <20131206171721 DOT GA7240 AT ednor DOT casa DOT cgf DOT cx> <CAKChYSqyXHXUh1GVNsOEZWPbS=RsObb_gOCLX5kycMFWej-mwQ AT mail DOT gmail DOT com> <20131206234833 DOT GC3154 AT phoenix> <CAKChYSrNhmza5TBZNQQnaAC2LKJz7G1MbJi-+1K97c=Z0h9CJQ AT mail DOT gmail DOT com> <CAKf2h5S8n+JX1LVbf+ZZDRUneJuiG0OQ9B9wTpr3WVj2gUkNSg AT mail DOT gmail DOT com> <CAKChYSrsuLrO=OxZqD7wSeti8-oGtZeYr5yy3rjxxQGU6zzuxg AT mail DOT gmail DOT com> <CAKf2h5S+b8kjuXm2bmuEwUGk9bLfJjq602-e_YYGhcptKd_XWQ AT mail DOT gmail DOT com> <20131209125119 DOT GJ2527 AT calimero DOT vinschen DOT de> <CAKChYSq8RTRpH3OprWSHKqWbT9POjHGmcMGRESqb+KXmVmecCQ AT mail DOT gmail DOT com> <CAKf2h5SNP3zck69kmA6NbPv6EdakMtnu=zbiviDu6fZ4DmW1iw AT mail DOT gmail DOT com>
From: =?ISO-8859-1?Q?Bj=F6rn_Kautler?= <Bjoern AT Kautler DOT net>
Date: Mon, 9 Dec 2013 15:14:05 +0100
Message-ID: <CAKChYSqV_2bC64OckU1Ff08NYt0mAwYz7A=NNmWqaUru9p86MQ@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id rB9EEvL2010854

The special handling of vi is just fine.
The whole problem is that not only the vi behaviour changed, but also
the vim behaviour.
Which is why I suggested the solutions I suggested.

2013/12/9 Frank Fesevur <ffes AT users DOT sourceforge DOT net>:
> 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
>

--
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