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:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=PiyVNEX21CSIEcL6B4Noe6nvyS+T9Z
	GAaG4FfN4HN0lUFf+L21NXrPgrA204vn4SCXGE/L7e4Oszki/SDEwCZTBWjKRDXn
	0WCsZn4bcUg2NgrFvZfrL9B/a8RL/HAAeDJRMikLRHqFuMkvSK1y2aqI51q7pFke
	pNp9oxiyXyq34=
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:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=l2vvzyAs2aZy/0PnV09tfOxSckM=; b=aD3n
	/Jhb8349DsZwgcX3PriVv5rF8QmTBv+KlXX4XyT2V931Bew4eqV443/6H3dERPk/
	H1BzqwSArqpzw/O97RFxAzPaqW1MbobAKzF0R5PGVAiuvZRrGvOQfVayL0mObak+
	cCq+x2T94AVI9dw9+JaZrqMsL38hsMLFQiC9wEg=
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=-0.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: mail.spocom.com
Date: Fri, 10 Apr 2015 13:35:20 -0700
From: Gary Johnson <garyjohn AT spocom DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.35: possible backspace key and arrow keys bug
Message-ID: <20150410203520.GB13043@phoenix>
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> <20150410192151 DOT GA13043 AT phoenix> <mg999s$hm9$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <mg999s$hm9$1@ger.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-IsSubscribed: yes

On 2015-04-10, René Berber wrote:
> On 4/10/2015 2:21 PM, Gary Johnson wrote:
> > On 2015-04-09, René Berber wrote:
> 
> >> Why vim on Cygwin doesn't install, or use if you add one, /etc/vimrc?
> > 
> > Executing
> >     $ vim --version
> > shows
> >        system vimrc file: "$VIM/vimrc"
> >          user vimrc file: "$HOME/.vimrc"
> >      2nd user vimrc file: "~/.vim/vimrc"
> >           user exrc file: "$HOME/.exrc"
> >       fall-back for $VIM: "/etc"
> >      f-b for $VIMRUNTIME: "/usr/share/vim/vim74"
> > From within vim,
> >     :echo $VIM
> > shows
> >     /usr/share/vim
> ...
> > So, Cygwin's vim looks for the system vimrc at /usr/share/vim/vimrc,
> > not /etc/vimrc.
> ...
> > Personally, I really like that Cygwin does not include a system
> > vimrc in its vim package.
> 
> Two points:
> 
> 1. Users expect things to work out-of-the-box.  As shown by this thread
> vim is not.

It does work out of the box.  It just may not be configured as you'd
like.  But your point is well taken.  If vim is pre-configured on
Red Hat or Ubuntu systems, then for most users it should probably be
pre-configured on Cygwin.  I can work around it.

> 2. If there is a standard, it should be used.  Moving from Linux to
> Cygwin should be transparent, but in the former there is an /etc/vimrc,
> in the later there isn't, and even more confusing: if you add one it
> doesn't work (for the reason you showed).

The Red Hat standard is /etc/vimrc.  The Ubuntu standard is
/usr/share/vim/vimrc.

> > I don't understand what you mean that the 5th line doesn't work and
> > has to be commented.
> 
> It means that if you leave it, vim will complain when you start it:
> 
> "Error detected while processing /etc/virc:
> line    5:
> E319: Sorry, the command is not available in this version: syntax on"

In most distributions, vi is vim-small or vim-tiny.  In Fedora and
Cygwin, vi is vim-small.  In Ubuntu, the vim version installed as vi
apparently depends on which vim package(s) you have installed and
may be vim-tiny or vim-huge.

The tiny and small versions do not support syntax highlighting.  See
the output of ":version".  Also see ":help :version" for a list of
which features are supported in which versions.  You should not
expect "syntax on" or any other vim command not found in the
original vi to work in /etc/virc.

> The point is: why does it work when in ~/.vimrc, and not on /etc/virc
> (not a typo, /etc/vimrc is not used at all, another deviation from the
> standard?).

Which configuration files are read depends on whether you execute
"vi" or "vim".

Regards,
Gary


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