New FAQ entry about RHEL/Centos compilation errors
Adding `::` as a semantic trigger for Ruby

Fixes #367.
Clarifying a comment.
Better completion in the middle of a word

For instance (`|` represents the cursor):
  1. Buffer state: `foo.|bar`
  2. A completion candidate of `zoobar` is shown and the user selects it.
  3. Buffer state: `foo.zoobar|bar` instead of `foo.zoo|bar` which is what the
  user wanted.

This commit resolves that issue.

It could be argued that the user actually wants the final buffer state to be
`foo.zoobar|` (the cursor at the end), but that would be much more difficult
to implement and is probably not worth doing.

Fixes #374.
Updating a FAQ item on Syntastic
Updating the error message for ycm_core loading
Fixed compilation under MSVC(11)
- compile both libs with /UNICODE and /MP
- moved shared flags & defines to root CMakeLists.txt
- fixed resolving EXTERNAL_LIBCLANG_PATH on Windows
- postbuild copy of libclang.dll
- change PATH_TO_LLVM_ROOT & EXTERNAL_LIBCLANG_PATH to PATH variables instead of BOOL options (for cmake-gui)
Merge pull request #385 from feed57005/master

Fixed compilation under MSVC(11)
Adding DLL as a valid extension for ycm_core

Fixes #395
Using the new 3.3 clang binaries in CMakeLists.txt
Use -j instead of -y on linux for tar
Using correct platform clang libs for linux
Using the new clang 3.3 headers
Updating docs to state clang 3.3 is preferred.
g:ycm_semantic_triggers now only adds new triggers

Fixes #164.
FAQ item for UltiSnips key conflict

Related to #381
Option to set min length for suggestions

Only works with the identifier completer. Fixes #387.
Don't call SyntasticCheck if not syntastic checker

If the user forced YCM to not register itself as the Syntastic checker, we
should not be calling SyntasticCheck since that would slow down everything.

Fixes #416
Minor formatting changes to docs
Encouraging the user to read the docs even more

Apparently we weren't encouraging enough before. Related to issue #415.