Ditto. Here was my "super-quick installation" experience on OS X:

1. Read through the full page of installation instructions.

2. Update to latest version of MacVim.

3. Go research Vundle because up until now, I've been happily using Pathogen. Install Vundle.

4. Update vimrc file for Vundle, add YCM.

5. Launch vim, note error saying YCM needs installation.

6. Run :BundleInstall, which tells me I should compile and impolitely adding "Read the docs!" (Which docs? The GitHub docs, which tell me I should only need to recompile in rare cases? Or the bundle's vim docs, which didn't exist on my system prior to running this command?)

7. Back to terminal, launch ./install.sh --clang-completer in the YCM directory.

8. Go fix breakfast, return. Compilation eventually completes, no errors.

9. Launch vim, which immediately crashes with error: Vim: Caught deadly signal ABRT

10. Give up and delete any trace of YCM.

In a perfect world maybe I would have an extra hour or two to debug this, run through some regressions but right now I don't. Sounds like a nice plugin, maybe I'll try again in the future.

> 9. Launch vim, which immediately crashes with error: Vim: Caught deadly signal ABRT

Had the same problem. There's something about this in the FAQ: One should delete and re-install python if it was installed through brew. (Doing this and recompiling YCM worked for me.)

The other gripe was: "Add YCM to vundle" ... without any mention of what exactly to add.

Then the thing started complaining about the missing .extra_ycm_something.py ...

You don't really need to completely uninstall homebrewed python. Just `brew unlink python` and after installation `brew link python`.

1. brew install vim cmake

2. git clone https://github.com/Valloric/YouCompleteMe.git ~/.vim/bundle/YouCompleteMe

3. cd ~/.vim/bundle/YouCompleteMe

4. ./install.sh --clang-completer

I already have the latest version of cmake installed via homebrew.

The problem appeared to be that YCM's install.sh script goes out of its way to determine the active version of python and link against its libraries[1].

For anyone with python installed via homebrew, that means it links to 2.7.3. Unfortunately, both MacVim and the homebrew version of vim link against the system python (2.7.2). As a result, loading YCM triggers an error resolving urandom and crashes vim.

[1] https://github.com/Valloric/YouCompleteMe/blob/master/instal...

I just had to rename vim in /usr/bin so it'd pick up the /usr/local/bin homebrewed version instead, but yeah, this.

That likely means your PATH is out of order, if ordered correctly /usr/local/bin should override /usr/bin. Can save you needing to do that in the future.

Hey, thanks!

But you had plenty of time to bitch about it? ;-)

Edit: It suddenly occurred to me just how reliant everyone now is on package managers. Once upon a time, I would think installing a dependency or two before compiling a new toy commonplace, if not expected. Nowadays... it's yak shaving.

Not that I'm no less guilty of this. I've even downloaded AUR helper tools because I'm too lazy to even wget a package and do a makepkg any longer.

The yak shaving part is not the steps described, but the steps not described that will end up being required.

Where you follow the given steps carefully and one fails because whichever version of something is not the right one, then you end up in a weird state where you have a hard time going back to how your setup was before, and you have to google things like "Compiler error: missing dependency foo.h" even though you can see that foo.h is right there. You then finally fixed the foo.h error to discover that you need to update Ruby for whatever reason, but the system doesn't pick up the version you installed with Homebrew anymore but is using the old default one, you then start updating Homebrew. Etc., etc. until you don't even know what you were trying to achieve in the first place and you are now super irritable.

(yes, I had a recent experience with that kind of yak shaving :))

Exactly.

Been there, done that, got a billion t-shirts and switched away from Linux to get away from this.

I'm pretty sure you can install it with Pathogen as normal. There are just two other points: (1) make sure you have the latest version of vim; (2) you just need to run an install script to finalize it. The script is in the bundle folder you create when cloning the git repo.

You better thank your lucky stars you aren't installing on Windows! Took me many days of tinkering to get this working correctly with clang support, and its still not all the way there yet.

Regardless, amazing vim plugin!