Optionally write OmniSharp stdout and stderr to log files
minor refactoring PR #2
Find a free port for OmniSharp if another OmniSharp is using the default port
Merge branch 'master' of https://github.com/Chiel92/YouCompleteMe into multiple_sln
Merge branch 'master' of https://github.com/Chiel92/YouCompleteMe into multiple_sln

Conflicts:
	python/ycm/completers/cs/cs_completer.py
Merge branch 'C#MultipleOmniSharps' of https://github.com/mispencer/YouCompleteMe into multiple_sln

Conflicts:
	python/ycm/completers/cs/cs_completer.py
style fixes
Add Unite to the filetype's blacklist
Merge pull request #465 from vheon/patch-1

Add Unite to the filetype's blacklist
Fixing compilation on Cygwin

Fixes #473.
Updating docs with new defaults for blacklist
Use debian6 package for 32bit llvm+clang, ubuntu one is actually 64bit

Fixes #474
Merge pull request #475 from jmesmon/fix474

Use debian6 package for 32bit llvm+clang, ubuntu one is actually 64bit
Fix crash: posting Vim message from thread

Vim is not thread-safe so posting a message to Vim from a non-GUI thread causes
a crash *sometimes*. I was aware of this problem before, but didn't catch this
instance of it in code review.

Fixes #479.
Minor code style fixes
More doc info for `g:ycm_confirm_extra_conf`
Using b:changedtick for change detection

For now, doing it just for detecting whether a change was made on move in insert
mode.

Using b:changedtick instead of our homebrew way of detecting the changed should
be both faster and more robust.
Only parsing file if changes detected

Previously we would do it on every CursorHold, buffer changed or not.

Fixes #485.
Revert to old way of tracking insert mode change

b:changedtick is incremented by the feedkeys() call which screws us up and
there doesn't seem to be a way around it that's worth the hassle.
Deleting some dead code