So for terminal Vim'ers:
1. copy the mvim script from MacVim to /usr/local/bin (or wherever)
2. ln -s /usr/local/bin/mvim vim (assuming you've ditched your old vim symlink)
Linking directly to the MacVim binary causes these sorts of issues[0].
Vim from Homebrew doesn't work though, something is wrong with the way Homebrew configures/builds Vim (don't know what though).
You can certainly build a Vim from source for Mac and have that work well with YCM, the only question is why would someone go through the trouble of doing so when MacVim does it for you.
Even if you prefer using Vim in the console and don't like the GUI, MacVim.app has a normal Vim binary inside it that you can call.
Ah okay - the README gave me a very different impression. Either way using the packaged MacVim binary via the mvim script is preferable, for reasons you've elaborated on.
> why would someone go through the trouble of doing so when MacVim does it for you.
Commandline lovers love trouble, are often not found browsing .dmg offerings?
* brew install vim
* alias vim="/usr/local/Cellar/vim/7.3.632/bin/vim"
* :BundleInstall 'Valloric/YouCompleteMe'
* Make the ycm_build directory:
cd ~
mkdir ycm_build
cd ycm_build
* Run cmake from the ycm_build dir:
cmake -G "Unix Makefiles" . ~/.vim/bundle/YouCompleteMe/cpp
And boom, YouCompleteMe is running for me.
Works amazing. Always had a problem with having to press a button to autocomplete. The cognitive reflection of "okay, I want help completing this word" usually defeats the speed improvement for me.
alias vim='/path/to/mvim -v' $ vim filename vim
https://github.com/search?q=%27editor+%3D%27++extension%3A.g...
What I usually do is maintain a set of symlinks in ~/bin/ (which is in my PATH) if they are not already in my PATH (or if I want them to override something else in my PATH, like HEAD builds of various things on occasion), and only use aliases to set default arguments (`ls --color=auto` for example).
error: There was a problem with the editor 'vi'