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:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=QwW+8M0YuqsHARebRrv+W0oL82Muo
	AwwWYGuiE1j4YR3UENBsVUsDBpmQWIe00Ocx9mZCNW2A0n5v0AKZNGPgV48DKh1u
	6Tzgw/rL6nNqeB4gFkjsyqaGpLYu8lRVbvnZHE96JxRVF0OnYlNaApkgpE17F5Ba
	AlXN9+KMhjW30Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Paul King <oaeinet AT gmail DOT com>
Date: Sat, 12 Oct 2013 15:56:51 -0400
Message-ID: <CAMp0Ogi3W614u9p4gTpPEE3yvA+LHp8BwdiWAjrNjD5BN1mO=w@mail.gmail.com>
Subject: Found out why vim/vundle didn't work
To: cygwin <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=ISO-8859-1

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

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.

Paul King

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