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:in-reply-to; q=dns; s=default; b=tarb 1hVMQZRIsFP8HvdY9M034o77MUCua5/DwG1Bi1q7NXHFuoS8lHXJUb/DMGFJ2e6H Y2ME9kwPYRC/awtR3yU1s1zFT0N3Z7P+/MyudhqlFnQLsq03CQEZcNWH89Ceamba dPwTRpu+m7av6aprEWd35cTlu4B6gXCeXIKvXyI= 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:in-reply-to; s=default; bh=/NIlzCkJZV lPRaYnFJ6pRWglFL8=; b=v+NBqV2ezL/1x/9Eygnte3m8Z+yCr2pSWVwMvItGXW HYAEp2HiYPD0+GpazMOXGBkn6mFqaL28GV4rk7x6TsRbnFg84DQtRVp+CnqkOiOF 6SuHuuQqk2u33WgS3MimNDIUVAczKduxYnH79wmo3LN4jFyKGBpMLnR9dU8R0wgN w= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=2.5 required=5.0 tests=AWL,BAYES_50,FSL_HELO_NON_FQDN_1,HELO_LOCALHOST,RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mail.spocom.com Date: Thu, 3 Oct 2013 10:40:03 -0700 From: Gary Johnson To: cygwin AT cygwin DOT com Subject: Re: VIM Vundle not working under Cygwin64 Message-ID: <20131003174003.GB989@phoenix> Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes On 2013-10-03, Paul King wrote: > Hello > > I have tried to get vim's vundle package to work under Cygwin64, and > it appears as though vim doesn't understand most of the package. > Vundle works under 32-bit Cygwin, but something in the way the 64-bit > version was compiled looks in the wrong place for vimrc. > > The 64-bit version (sorry I forget the version number (I uninstalled > it), but it is the one under the very latest 64-bit distro) thinks > that > vimrc resides under ~/.vim/vimrc (a directory in my case). It does not > look at my ~/.vimrc file at all. I got this info using :version The latest 64-bit Cygwin vim package is 7.3.1314-1. Since version 7.3.1178, vim looks for your personal configuration file first in ~/.vimrc, then in ~/.vim/vimrc. I have my actual vimrc file in ~/.vim/vimrc and currently symlink to it from ~/.vimrc so that I can run older versions of vim. When I run vim-7.3.1314-1 on 64-bit Cygwin, it says that $MYVIMRC is $HOME/.vimrc. ":scriptnames" also shows ~/.vimrc as the only vimrc sourced. So, Cygwin's 64-bit Vim is working just fine for me. > When I force it to do so (vim -u ~/.vimrc filename), I get a ton of > errors as it does not seem to understand most of the Vundle commands. > That could also be from the fact that it might be an older version of > vim, but since I uninstalled it, I can't be sure. Are you sure you're running the full version of vim? ":version" should show this at the top: :version VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 13 2013 01:07:02) Included patches: 1-1314 Compiled by <#################> Huge version without GUI. Features included (+) or not (-): [It turns out that including the real "Compiled by" string causes this message to be rejected by the list server because that string includes an e-mail address.] It looks to me like you might be running the minimal version of vim. Try this command. $ cygcheck -cd | grep vim vim 7.3.1314-1 vim-common 7.3.1314-1 vim-minimal 7.3.1314-1 If that looks the same on your system, would you post the errors you -- 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