Hot answers tagged

3

In my case it was good enough to comment out the fullscreen part of the extended.vim config file found under ~/.vim_runtime/vimrcs/extended.vim. Look for the if has("gui_macvim") in that file and comment out that entire block and you should be able to start MacVim in windows mode. Side note, I've also turned off the native fullscreen support for MacVim ...


2

Ah, lord, somebody in #vim on Freenode helped me out: that line going around is bugged, because ; doesn't mean subsequent-command in Vim. The following works as intended: mvim --remote-silent +":%line | silent foldo!" "%file"


1

I was hitting this problem after upgrading to 10.11, and the accepted solution didn't work for me. I found that the problem was not with the updated MacVim install, but rather that the mvim script was finding an old MacVim binary I didn't even know I had rather than the freshly-updated one. So, if anyone hits this problem and the above fix doesn't work, ...


1

The easiest way I found was to add the file I needed to the system vim file that MacVim created on installation. This file can be found using :scriptnames command. I needed to use pathogen and it was not working placing it in my .vim file in the home directory. I placed the pathogen.vim in the system vim/autoload directory and then pathogen worked without ...


1

My two cents, I run this whenever upgraded my python via homebrew. brew reinstall vim --HEAD --with-cscope --with-lua --override-system-vim brew reinstall macvim --HEAD --with-cscope --with-lua --override-system-vim


1

I work on Windows 10 and :recover didn't find a swap file. vim -r listed the swap file from the last edit session (also never saved) named _.swp. Recovering was able with :recover _.



Only top voted, non community-wiki answers of a minimum length are eligible