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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=qVOvNgu42KaoDwnt
	w5Yqjx2nDjmGUOP5ujAh2AF0z69mA+TfP/rc1fems8sVVS+wi0lMsvpnAtY7vHJn
	GQsOG5R4/uJxqqAl4jJgbUmsp3Ozse1m1k94kM5oW5IeiXRb1c01/cQA9Mj1Rg3g
	QbpwD59LYjhpEIhkfXcwUGEuQZw=
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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=hC+FRXEbsqcFKLVNXM0QPB
	PHVd8=; b=m+azc64GuZPQmMRyif+GhhWMFJg7zlx688NNx4ua5qw7bWewsmHbEg
	xNDfqJAhNLs4sUCrZEFY0MgIrf0znDhuzqU1KiD34JgF4bMQqugOv7quQPVaCk/R
	Nxny1trMNJ5p48HckYx4zedBdF3wx3ACtzRNVhxTebZT1klcDQhbw=
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: Yes, score=6.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_PSBL,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtpback.ht-systems.ru
Date: Mon, 14 Oct 2013 08:59:19 +0400
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: Andrey Repin <cygwin AT cygwin DOT com>
Message-ID: <1914801213.20131014085919@mtu-net.ru>
To: Paul King <oaeinet AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Found out why vim/vundle didn't work
In-Reply-To: <CAMp0Ogi3W614u9p4gTpPEE3yvA+LHp8BwdiWAjrNjD5BN1mO=w@mail.gmail.com>
References: <CAMp0Ogi3W614u9p4gTpPEE3yvA+LHp8BwdiWAjrNjD5BN1mO=w AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Paul King!

> I sent an earlier message to the list (or possibly to the vim list)
> about my problems in getting the vundle distro to work under the vim
> text editor. I am glad to report that the problem is solved, and this
> is what I found:

> This is a "cygwin" problem, although not necessarily a bug; more like
> a PEBCAK problem in the package selection stage, as there are 3 vim
> packages to choose from.

> The "vim" command is a different "vim" than the "vi" command. Both are
> "vim", but come from different vim packages. In Linux and other *nix
> systems, vi is symbolically linked to vim, but not in this case.

It is _commonly_ linked to vim, but that really only because most of the
distros you've worked with have full version of vim installed by default.
Cygwin offers vim (full) and vim-minimal packages.
If you intend to use full one, I suggest you remove vim-minimal and make a
familiar symlink for vi.
You can find more details, and the reason behind the change, in the list
archives for this year.

> These
> are different copies of vim, and both look in different places for the
> .*rc file. I found that "vi" looks first in ~/.virc and second in
> ~/.vim/vimrc. When you install vundle. the second place is a
> directory, causing "vi" to choke. Even when that is corrected, it
> doesn't know how to handle the Bundle command, and you get a wild
> flurry of error messages.

That is to be expected.

> vim, however, looks first in ~/.vimrc which exists, and in turn
> sources files under ~/.vim/vimrc. It waits a few moments, then opens
> your file. This is consistent with my experience with vim/vundle under
> other OS'es.

> So, for me it was just a matter of logging in with my Administrator
> account, then moving "vi" to "_vi"; then agreeing with custom, linking
> vim symbolically to vi.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 14.10.2013, <08:55>

Sorry for my terrible english...


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