Errors setting up on Windows 7 (g:vundle_last_status undefined)

[MatthiasKauer]

Hi,
this is similar to #399 ,but the fixes there seem to work only for an older version.

My minimal _vimrc

set nocompatible " disable vi compatibility (emulation of old bugs)

"make sure that we can write in temp folder on Windows
"set directory=.,$TEMP

filetype off "vundle needs this; will be turned on later
set runtimepath+=$HOME/vimfiles/bundle/Vundle.vim
let path='~/vimfiles/bundle'
call vundle#begin(path)


Plugin 'gmarik/Vundle.vim' " must be installed manually via git clone on first run!
Plugin 'sjl/gundo.vim'
call vundle#end()            " required

"syntax highlightign and filetype detection
syntax on                           " syntax highlighing
" filetype on                          " try to detect filetypes
filetype plugin indent on    " enable loading indent file for filetype

The fix for the temp folder is disabled, but I'm calling a file from a writable directory (if not: different swap file related errors, but ok). Errors after :PluginInstall are:

I followed the discussion around #294 and #175 . There, people had similar errors and solved them by setting their shell to bash in vim. I am not sure how this applies to my situation on Win7 however.

I also tried the _vimrc suggested in #399 . It didn't work either because I couldn't adjust it to my _vimrc + $Home/vimfiles/bundle setup and vundle#rc seems not to be there anymore.

Now I'm stuck. Can you suggest what I should look into next? Is there maybe an issue with capital letters or punctuation in folder names on Windows (github repo name seems to have changed from vundle to Vundle.vim judging from older issues)?

PS:

C:\Users\matthias.kauer\vimfiles\bundle>git --version
git version 1.9.5.msysgit.0

C:\Users\matthias.kauer\vimfiles\bundle>curl --version
curl 7.30.0 (i386-pc-win32) libcurl/7.30.0 OpenSSL/0.9.8{ zlib/1.2.7
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM SPNEGO SSL SSPI libz

[MatthiasKauer]

tried to add the trailing slash as suggested in #469 but nothing changed.

[ModeEngage]

I've been running into the same issue on Windows 7, and my exhaustive search of the internet has lead me here. Interestingly, I've found another symptom. When I run a :PluginInstall, the .git folder in my current working directory gets wholesale replaced with no user input.

For reference:

> curl --version
curl 7.16.4 (unknown-pc-win32) libcurl/7.16.4
Protocols: tftp ftp telnet dict ldap http file
Features: Largefile
> git version
git version 1.9.5.msysgit.0

[annagrram]

I see nobody replied to this issue for several days, so I decided to jump to a Windows machine and give it a try. Indeed, the problem was there.

After some investigation, I've found that the Antivirus sandbox was the problem.
Try checking your Antivirus settings and make sure to add Vim/gVim and its child processes to the trusted applications.

[MatthiasKauer]

I was going to test turning off my Antivirus, but on my Windows computer at home it wasn't even necessary. Hmm. I'll have to check again on Monday.
This is still on commit 7d9b108.

[MatthiasKauer]

Ok, back at work now; seems like the repo was updated to cfd3b2d in the meantime.
I tested with this and the one before; no big difference on this issue.

On my home installation that shares the configuration files, everything is fine. On my work, the error messages haven't really changed. I did deactivate the virus scanner temporarily, but it didn't help either.

My guess is now that there is an issue with long usernames or dots in usernames and the temp folder where vundle stores some kind of status. At home, I'm 'matthias', at work, I am 'matthias.kauer'.
Does this help somehow?

Note that plugins are installed and appear to work anyway, but it's very confusing.

[annagrram]

Ok. Let's try to narrow down the problem.
Can you do the following steps and report the results?

1. In VIM
   1. :cd $TMP
   2. :w tst
2. In CMD
   1. cd %TMP%
   2. git clone https://github.com/gmarik/Vundle.vim
3. Check the logs of the Antivirus program for blocked operations. Just to make sure.
4. Make sure you don't have other security programs which might interfere.

[ModeEngage]

I had no problem writing to $TMP from vim.

CMD Output:

C:\Users\REDACTED~1\AppData\Local\Temp>git clone https://github.com/gmarik/Vundle.vim
Cloning into 'Vundle.vim'...
remote: Counting objects: 2880, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 2880 (delta 0), reused 0 (delta 0), pack-reused 2873
Receiving objects: 100% (2880/2880), 853.75 KiB | 0 bytes/s, done.
Resolving deltas: 100% (984/984), done.
Checking connectivity... done.

PowerShell Output:

C:\Users\REDACTED\AppData\Local\Temp> git clone https://github.com/gmarik/Vundle.vim
Cloning into 'Vundle.vim'...
remote: Counting objects: 2880, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 2880 (delta 0), reused 0 (delta 0), pack-reused 2873R
Receiving objects: 100% (2880/2880), 853.75 KiB | 902.00 KiB/s, done.
Resolving deltas: 100% (984/984), done.
Checking connectivity... done.

[annagrram]

@ModeEngage Have you chcked your Antivirus (or any other security software) for blocked operations or tried to disable them temporarily?

[ModeEngage]

Looked at all of the logs anti-virus has to offer me -- saw nothing indicating I'd had any operations blocked.

[annagrram]

Another obeservation: I can reproduce this problem also when there's a problem with the Git commands. It doesn't act like in Linux, for example, which is a problem, but let's check. Go to the bundle directory and into Vundle.vim. Then run:

1. git status
2. git remote -v

Please post the result.

[ModeEngage]

C:\Users\redacted\home\vimfiles\bundle\Vundle.vim [master]> git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working directory clean
C:\Users\redacted\home\vimfiles\bundle\Vundle.vim [master]> git remote -v
origin  https://github.com/gmarik/Vundle.vim.git (fetch)
origin  https://github.com/gmarik/Vundle.vim.git (push)
C:\Users\redacted\home\vimfiles\bundle\Vundle.vim [master]>

[annagrram]

Looks fine for Vundle.vim
Can you check your other plugins, or disable the rest and just leave Vundle and try to :PluginUpdate?

[MatthiasKauer]

Results are similar on my machine; no issues writing to temp. git output looks identical, but I don't really know what to make of that.

Another idea: is it possible that there are old files created during previous unsuccessful installations that are now lurking somewhere? Can we clear something to get back to a clean slate?

:cd
:pwd
C:\Users\matthias.kauer\AppData\Local\Temp
:w
"tst" [New] 9L, 537C written


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\matthias.kauer>cd %TMP%

C:\Users\MATTHI~1.KAU\AppData\Local\Temp>git clone https://github.com/gmarik/Vun
dle.vim
Cloning into 'Vundle.vim'...
remote: Counting objects: 2880, done.
remote: Total 2880 (delta 0), reused 0 (delta 0), pack-reused 2880
Receiving objects: 100% (2880/2880), 851.76 KiB | 432.00 KiB/s, done.
Resolving deltas: 100% (986/986), done.
Checking connectivity... done.

C:\Users\MATTHI~1.KAU\AppData\Local\Temp>


C:\Users\MATTHI~1.KAU\vimfiles\bundle\Vundle.vim>git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working directory clean

C:\Users\MATTHI~1.KAU\vimfiles\bundle\Vundle.vim>git remote -v
origin  https://github.com/gmarik/Vundle.vim.git (fetch)
origin  https://github.com/gmarik/Vundle.vim.git (push)

[MatthiasKauer]

Another test: BundleInstall 'tpope/vim-sensible' worked just fine for me and I even saw the corresponding tmp file that PluginUpdate or Install without argument seems unable to create.
I assume that I'd have to add sensible to my vimrc manually after that, but I didn't test that.

[annagrram]

Vundle seems ok, but the problem could have happened with any other problematic plugin.
To test that, can you please disable all other plugins but Vundle and try to :PluginUpdate?
If that works, try to add one plugin a time until you find the culprit.