Message-ID: <457657A0.8050500@byu.net>
Date: Tue, 05 Dec 2006 22:39:44 -0700
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Setting vim to nocompatible by default in Cygwin [Attn base-files  maintainer]
References: <20061205212654.74613.qmail@web51015.mail.yahoo.com> <31b7d2790612051406k781735e3lb4d096ef5cf38142@mail.gmail.com>
In-Reply-To: <31b7d2790612051406k781735e3lb4d096ef5cf38142@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to DePriest, Jason R. on 12/5/2006 3:06 PM:
> 
> It was indeed confusing to me when I started using Cygwin.
> 
> I copied my vimrc file from my Debian GNU/Linux system to my Cygwin
> system and that fixed it (and a few other issues I have with the
> default vim configuration).

Is it worth the base-files maintainer providing a default .vimrc file that
gets installed alongside all the other default .*rc files for new users?
My understanding of this issue is that it is not the compilation of vim
that differs from typical Linux distros, but our selection of default rc
file settings (or lack thereof).

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFdlef84KuGfSFAYARAkJqAKCxQlC2kfCOPr29A8ZORkpO/wK5KACgyYXC
hfQyJPn9wPOdLFPZnuLM28I=
=fRFY
-----END PGP SIGNATURE-----

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