This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Found out why vim/vundle didn't work
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Paul King <oaeinet at gmail dot com>, cygwin at cygwin dot com
- Date: Mon, 14 Oct 2013 08:59:19 +0400
- Subject: Re: Found out why vim/vundle didn't work
- Authentication-results: sourceware.org; auth=none
- References: <CAMp0Ogi3W614u9p4gTpPEE3yvA+LHp8BwdiWAjrNjD5BN1mO=w at mail dot gmail dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
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@yandex.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