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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=SuO7Ywu5QR1Ryp9QjE3afLSLmiofOXCICHa+Dy0gaEy/18oSvnMuH
	+EDpqD8JbEtVzjXl1d6sXhwb3LB9NGbwkM5NAIkggfl+jfQ8/4rFrxdI9RbeNgUP
	AEybBAvRpWgMuoAP6PkGFtdi34oeVbQYqwG1gRZepiprfjdyd+RV6o=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=ztyVgmCBAzRRDD5KYMoHokP6r1Y=; b=flcS+F2n+YLGXWC57/BpJotK5JdA
	oHCr7rIGgWo0mYM+V0V6bg1a5FdF8n+LTILuX2R6limE0ZkdhM3V9lO0ipghHSaF
	tKWdo4JeLlSG8mHzaU/QRSn7mlhXs677p81F69ZDsMmPkpZkz1AwoowD2UjEqD0Z
	Ox4ejfNQSOtbYD4=
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=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 9 Apr 2015 21:25:46 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.35: possible backspace key and arrow keys bug
Message-ID: <20150409192546.GD6901@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAMOkCRZ4Tdg+UoydTj+ntXyyFvbhk8ug6A+LXAG3+zOw4UfuTw AT mail DOT gmail DOT com> <20150408221622 DOT GK20741 AT dinwoodie DOT org> <CAF+j1MP-dtu66bq_kj5qQ7W7m7m64A1RvwW=Cga6-o1W2X5JUw AT mail DOT gmail DOT com> <20150409173434 DOT GC6901 AT calimero DOT vinschen DOT de> <mg6hq4$gpo$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="cQXOx3fnlpmgJsTP"
Content-Disposition: inline
In-Reply-To: <mg6hq4$gpo$1@ger.gmane.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

--cQXOx3fnlpmgJsTP
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  9 13:51, Ren=C3=A9 Berber wrote:
> On 4/9/2015 12:34 PM, Corinna Vinschen wrote:
> > On Apr  9 09:54, Weston Turner wrote:
> >> I corroborate the original poster's experience with this issue.
> >>=20
> >> Steps to reproduce the issue: for example open a file with vim=20
> >> under Cygwin, press: up, up, down, down, left, left, right,
> >> right. Vim under Cygwin places:
> >>=20
> >> C C D D B B A A
> >>=20
> >> in the file due to the arrow keys being pressed. Vim under bash
> >> on Linux or the Mac terminal does not treat the arrow keys as
> >> file input, but rather simply uses them to move the cursor about
> >> in the file.
> >=20
> > WJFFM, as on Linux, in command mode as well as in insert mode.
>=20
> You probably have a .vimrc on Cygwin, and the same or /etc/vimrc on Linux.

I have a.vimrc, yes.

>=20
> The real question:
>=20
> Why vim on Cygwin doesn't install, or use if you add one, /etc/vimrc?
>=20
> On Linux I have one with the following contents (which fixes the
> thread problem):
>=20
> " Begin /etc/vimrc
>=20
> set nocompatible
> set backspace=3D2
> syntax on
> set background=3Ddark
> if (&term =3D=3D "iterm") || (&term =3D=3D "putty")
>   set background=3Ddark
> endif
>=20
> " End /etc/vimrc
>=20
> The 5th line doesn't work with the version installed on Cygwin, so you
> have to comment it; but it would be nice to also have syntax highlighting.

Indeed.  I just tested this by moving my ~/.vimrc to /etc/vimrc and
then /etc/virc, and in both cases syntax highlighting is not activated
even though a `set nocompatible' preceeds `syntax on', while the same
works fine on Fedora.

Yaakov, any idea?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--cQXOx3fnlpmgJsTP
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJVJtI6AAoJEPU2Bp2uRE+gP4EP/idsZ9tE46Ex2Jnq6/O66e8W
Flq6E3xnY1E/30rWr/yqAe1goAB1Bnq32T81HsqHdIKAD+OXXtWvPxST664eRlT3
xZLI897netEhXzPR5SyFxTDtkNb4ReE5uypthNMYinArV6Zrv6YcA+t9kpmx1k7M
JudVrQSkx+Q3D5Fx6agL0QpMdxUHzDdiiQIkeAeVUrfvoSi4clxpbEoADiP4XfBW
9Z+ImCzwdKLwrg0b6YUfAEx313aY+IyYdYbss47x7ZRcPdlgghCEF2/mh30p3rQW
JXhdwBQ9MLPyfCVe8ncx4Lk6vX5UG36s94pK6EVGkZe9O5o5FGTq5g2sRhavxXzG
zpZMuH+b+HxRDRkTncfjfhDt7GfUhl2LS0LOPT0hbDi7B0nM6soQaFitHW+RhOZ7
mCKtQNQWCMfwnnlYY08g6YiAJMSExpk7Lr3ffc5huzbBrJuKZ/QZe2xfkAqirZ4n
5nlUMA8qyCpUhRFERQn3rlhn+g1N1jBsZuR8WRtMgSLPhyQ8XdUFDHEhSEGJxBIF
PCW03Hj7rna30mXZ8qJwg77nuU4blxJTHKqAuM/h5Mqd+yFUEKW+OMdcIljQDGOO
2B0f4jJRihLHUuHNscxeS48wSxfgZXh+5sF92h9HE7wkWC2TX3qrhJE6po6aVtzB
ohgC9t6sHRKnblPerXPW
=V9Kx
-----END PGP SIGNATURE-----

--cQXOx3fnlpmgJsTP--