BundleInstall kills Windows Gvim 7.3

[eater]

I have installed Vundle on Windows according to the instructions. When I run BundleInstall from the command line, the Vundle split opens and it starts going down the list, but as soon as it reaches a bundle that's not yet installed, Windows 7 pops up an error: "Vi Improved - A Text Editor has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

How can I troubleshoot this?

[gmarik]

Hm, that's a weird one...
If you could provide me your .vimrc would take a look.

And now I need a Windows 7 Virtual Box's image )
Gonna be fun!

[eater]

.vimrc is just

set runtimepath+=$HOME/.vim,$HOME/.vim/after
source $HOME/vimrc

And then $HOME/vimrc is 730 lines of boring customizations that I can upload somewhere if it'll help. It leads off with:

filetype off
source ~/.vim/bundles.vim
filetype plugin indent on
syntax on

And bundles.vim is:

set nocompatible          
filetype off                  

set rtp+=$HOME/.vim/bundle/vundle/
call vundle#rc()

Bundle 'gmarik/vundle'
Bundle 'tpope/vim-surround'
Bundle 'tpope/vim-repeat'
Bundle 'tpope/vim-unimpaired'
Bundle 'scrooloose/nerdcommenter'
Bundle 'scrooloose/nerdtree'
Bundle 'sjl/gundo.vim'
Bundle 'xolox/vim-notes'
Bundle 'chrisbra/histwin.vim'
Bundle 'rygwdn/ultisnips'
Bundle 'wincent/Command-T'
Bundle 'kien/ctrlp.vim'
Bundle 'jceb/vim-orgmode'
Bundle 'mhz/vim-matchit'
Bundle 'eater/vimroom'
Bundle 'vimoutliner/vimoutliner'

"Colors
Bundle 'vim-scripts/dw_colors'
Bundle 'vim-scripts/asu1dark.vim'
Bundle 'vim-scripts/peaksea'

" from vim-scripts repo
Bundle 'vim-scripts/mru.vim'
"Bundle 'vim-scripts/project.vim'
"Bundle 'vim-scripts/writebackup.vim'
"Bundle 'vim-scripts/writebackupVersionControl.vim'
Bundle 'vim-scripts/closetag.vim'
Bundle 'vim-scripts/utl.vim'
Bundle 'vim-scripts/CSApprox'

filetype plugin indent on     

[eater]

Before you get too deep into your Virtualbox, it's possible that the Windows Vundle was dealing with some plugin directories that were partly but not fully copied from another installation, such as a bundle/vim-surround/ that contained doc/ but nothing else. I am away from my Windows machine for a few days (yay!) but I'll check that possibility out next week.

[gmarik]

It's unlikely,
but yeah, please let me know if you can verify that somehow.
Thanks!

[eater]

No, that wasn't it.

[gudezhi]

I met the same problem.

After debug to the vundle installer script, I found the problem at the func below.

func! s:log(str) abort
call add(g:vundle_log, '['.strftime("%y%m%d %T").'] '.a:str)
return a:str
endf

In Vimdoc, there is "the {fomat} of "strftime" depends on your system, thus this is not portable!"
So...is there some idea to fix it?

[gmarik]

wow @gudezhi, thanks for debugging this!

So...is there some idea to fix it?

How about dropping timestamping?

[gmarik]

Or just use windows compatible formatting

[gudezhi]

Not at all~
It sounds well enough to use windows compatible formatting

[gmarik]

@gudezhi, could you possibly play with format that works for you?
Just let me know which one works and i'll add it to Vundle, or you can just send pull request if you like )
Thanks!

[gudezhi]

@gmarik, It seems like "%T" doesn't work, but "%H:%M:%S" can work well.
My system is WinXP sp3, local is jp.

[eater]

Nice! Changing %T to %H:%M:%S does the trick for me.

[gmarik]

Cool, i'll push fix soon

[gmarik]

%T replaced with %H:%M:%S, let me know if that works for you!

[eater]

I had to delete and reinstall the Vundle package, which was giving errors when it tried to update itself, but having done that all is well on Windows and Linux, thanks!