diff --git a/doc/youcompleteme.txt b/doc/youcompleteme.txt index 4a8e235ebc..0ee3fbb50b 100644 --- a/doc/youcompleteme.txt +++ b/doc/youcompleteme.txt @@ -14,48 +14,50 @@ Contents ~ 3. General Semantic Completion Engine Usage |youcompleteme-general-semantic-completion-engine-usage| 4. C-family Semantic Completion Engine Usage |youcompleteme-c-family-semantic-completion-engine-usage| 5. Python semantic completion |youcompleteme-python-semantic-completion| - 6. Semantic completion for other languages |youcompleteme-semantic-completion-for-other-languages| - 7. Writing New Semantic Completers |youcompleteme-writing-new-semantic-completers| - 8. Syntastic integration |youcompleteme-syntastic-integration| + 6. C# semantic completion |youcompleteme-c-semantic-completion| + 7. Semantic completion for other languages |youcompleteme-semantic-completion-for-other-languages| + 8. Writing New Semantic Completers |youcompleteme-writing-new-semantic-completers| + 9. Syntastic integration |youcompleteme-syntastic-integration| 7. Commands |youcompleteme-commands| - 1. The ':YcmForceCompileAndDiagnostics' command |:YcmForceCompileAndDiagnostics| - 2. The ':YcmDiags' command |:YcmDiags| - 3. The ':YcmShowDetailedDiagnostic' command |:YcmShowDetailedDiagnostic| - 4. The ':YcmDebugInfo' command |:YcmDebugInfo| - 5. The ':YcmCompleter' command |:YcmCompleter| + 1. The |:YcmForceCompileAndDiagnostics| command + 2. The |:YcmDiags| command + 3. The |:YcmShowDetailedDiagnostic| command + 4. The |:YcmDebugInfo| command + 5. The |:YcmCompleter| command 8. YcmCompleter subcommands |youcompleteme-ycmcompleter-subcommands| - 1. The 'GoToDeclaration' subcommand |GoToDeclaration| - 2. The 'GoToDefinition' subcommand |GoToDefinition| - 3. The 'GoToDefinitionElseDeclaration' subcommand |GoToDefinitionElseDeclaration| - 4. The 'ClearCompilationFlagCache' subcommand |ClearCompilationFlagCache| + 1. The |GoToDeclaration| subcommand + 2. The |GoToDefinition| subcommand + 3. The |GoToDefinitionElseDeclaration| subcommand + 4. The |ClearCompilationFlagCache| subcommand 9. Options |youcompleteme-options| - 1. The 'g:ycm_min_num_of_chars_for_completion' option |g:ycm_min_num_of_chars_for_completion| - 2. The 'g:ycm_filetype_whitelist' option |g:ycm_filetype_whitelist| - 3. The 'g:ycm_filetype_blacklist' option |g:ycm_filetype_blacklist| - 4. The 'g:ycm_filetype_specific_completion_to_disable' option |g:ycm_filetype_specific_completion_to_disable| - 5. The 'g:ycm_register_as_syntastic_checker' option |g:ycm_register_as_syntastic_checker| - 6. The 'g:ycm_allow_changing_updatetime' option |g:ycm_allow_changing_updatetime| - 7. The 'g:ycm_complete_in_comments' option |g:ycm_complete_in_comments| - 8. The 'g:ycm_complete_in_strings' option |g:ycm_complete_in_strings| - 9. The 'g:ycm_collect_identifiers_from_comments_and_strings' option |g:ycm_collect_identifiers_from_comments_and_strings| - 10. The 'g:ycm_collect_identifiers_from_tags_files' option |g:ycm_collect_identifiers_from_tags_files| - 11. The 'g:ycm_seed_identifiers_with_syntax' option |g:ycm_seed_identifiers_with_syntax| - 12. The 'g:ycm_add_preview_to_completeopt' option |g:ycm_add_preview_to_completeopt| - 13. The 'g:ycm_autoclose_preview_window_after_completion' option |g:ycm_autoclose_preview_window_after_completion| - 14. The 'g:ycm_autoclose_preview_window_after_insertion' option |g:ycm_autoclose_preview_window_after_insertion| - 15. The 'g:ycm_max_diagnostics_to_display' option |g:ycm_max_diagnostics_to_display| - 16. The 'g:ycm_key_list_select_completion' option |g:ycm_key_list_select_completion| - 17. The 'g:ycm_key_list_previous_completion' option |g:ycm_key_list_previous_completion| - 18. The 'g:ycm_key_invoke_completion' option |g:ycm_key_invoke_completion| - 19. The 'g:ycm_key_detailed_diagnostics' option |g:ycm_key_detailed_diagnostics| - 20. The 'g:ycm_global_ycm_extra_conf' option |g:ycm_global_ycm_extra_conf| - 21. The 'g:ycm_confirm_extra_conf' option |g:ycm_confirm_extra_conf| - 22. The 'g:ycm_extra_conf_globlist' option |g:ycm_extra_conf_globlist| - 23. The 'g:ycm_filepath_completion_use_working_dir' option |g:ycm_filepath_completion_use_working_dir| - 24. The 'g:ycm_semantic_triggers' option |g:ycm_semantic_triggers| - 25. The 'g:ycm_cache_omnifunc' option |g:ycm_cache_omnifunc| + 1. The |g:ycm_min_num_of_chars_for_completion| option + 2. The |g:ycm_min_num_identifier_candidate_chars| option + 3. The |g:ycm_filetype_whitelist| option + 4. The |g:ycm_filetype_blacklist| option + 5. The |g:ycm_filetype_specific_completion_to_disable| option + 6. The |g:ycm_register_as_syntastic_checker| option + 7. The |g:ycm_allow_changing_updatetime| option + 8. The |g:ycm_complete_in_comments| option + 9. The |g:ycm_complete_in_strings| option + 10. The |g:ycm_collect_identifiers_from_comments_and_strings| option + 11. The |g:ycm_collect_identifiers_from_tags_files| option + 12. The |g:ycm_seed_identifiers_with_syntax| option + 13. The |g:ycm_add_preview_to_completeopt| option + 14. The |g:ycm_autoclose_preview_window_after_completion| option + 15. The |g:ycm_autoclose_preview_window_after_insertion| option + 16. The |g:ycm_max_diagnostics_to_display| option + 17. The |g:ycm_key_list_select_completion| option + 18. The |g:ycm_key_list_previous_completion| option + 19. The |g:ycm_key_invoke_completion| option + 20. The |g:ycm_key_detailed_diagnostics| option + 21. The |g:ycm_global_ycm_extra_conf| option + 22. The |g:ycm_confirm_extra_conf| option + 23. The |g:ycm_extra_conf_globlist| option + 24. The |g:ycm_filepath_completion_use_working_dir| option + 25. The |g:ycm_semantic_triggers| option + 26. The |g:ycm_cache_omnifunc| option 10. FAQ |youcompleteme-faq| - 1. I get a linker warning regarding 'libpython' on Mac when compiling YCM |libpython| + 1. I get a linker warning regarding |libpython| on Mac when compiling YCM 2. I get a weird window at the top of my file when I use the semantic engine |youcompleteme-i-get-weird-window-at-top-of-my-file-when-i-use-semantic-engine| 3. It appears that YCM is not working |youcompleteme-it-appears-that-ycm-is-not-working| 4. I cannot get the Syntastic integration to work |youcompleteme-i-cannot-get-syntastic-integration-to-work| @@ -68,13 +70,16 @@ Contents ~ 11. I have a Homebrew Python and/or MacVim; can't compile/SIGABRT when starting |youcompleteme-i-have-homebrew-python-and-or-macvim-cant-compile-sigabrt-when-starting| 12. Vim segfaults when I use the semantic completer in Ruby files |youcompleteme-vim-segfaults-when-i-use-semantic-completer-in-ruby-files| 13. I get 'LONG_BIT definition appears wrong for platform' when compiling |LONG_BIT-definition-appears-wrong-for-platform| - 14. I get 'Vim: Caught deadly signal SEGV' on Vim startup |Vim:-Caught-deadly-signal-SEGV| - 15. YCM does not read identifiers from my tags files |youcompleteme-ycm-does-not-read-identifiers-from-my-tags-files| - 16. 'CTRL-U' in insert mode does not work |CTRL-sub-U| - 17. Why isn't YCM just written in plain VimScript, FFS? |youcompleteme-why-isnt-ycm-just-written-in-plain-vimscript-ffs| - 18. Why does YCM demand such a recent version of Vim? |youcompleteme-why-does-ycm-demand-such-recent-version-of-vim| - 19. I get annoying messages in Vim's status area when I type |youcompleteme-i-get-annoying-messages-in-vims-status-area-when-i-type| - 20. Nasty bugs happen if I have the 'vim-autoclose' plugin installed |vim-sub-autoclose| + 14. I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling |libpython2.7.a-...-relocation-R_X86_64_32| + 15. I get 'Vim: Caught deadly signal SEGV' on Vim startup |Vim:-Caught-deadly-signal-SEGV| + 16. YCM does not read identifiers from my tags files |youcompleteme-ycm-does-not-read-identifiers-from-my-tags-files| + 17. 'CTRL-U' in insert mode does not work |CTRL-sub-U| + 18. YCM conflicts with UltiSnips TAB key usage |youcompleteme-ycm-conflicts-with-ultisnips-tab-key-usage| + 19. Why isn't YCM just written in plain VimScript, FFS? |youcompleteme-why-isnt-ycm-just-written-in-plain-vimscript-ffs| + 20. Why does YCM demand such a recent version of Vim? |youcompleteme-why-does-ycm-demand-such-recent-version-of-vim| + 21. I get annoying messages in Vim's status area when I type |youcompleteme-i-get-annoying-messages-in-vims-status-area-when-i-type| + 22. Nasty bugs happen if I have the 'vim-autoclose' plugin installed |vim-sub-autoclose| + 23. Is there some sort of YCM mailing list? I have questions |youcompleteme-is-there-sort-of-ycm-mailing-list-i-have-questions| 11. Contact |youcompleteme-contact| 12. License |youcompleteme-license| 13. References |youcompleteme-references| @@ -90,11 +95,11 @@ Vim. It has several completion engines: an identifier-based engine that works with every programming language, a semantic, Clang [3]-based engine that provides native semantic code completion for C/C++/Objective-C/Objective-C++ (from now on referred to as "the C-family languages"), a Jedi [4]-based -completion engine for Python and an omnifunc-based completer that uses data -from Vim's omnicomplete system to provide semantic completions for many other -languages (Ruby, PHP etc.). +completion engine for Python, an OmniSharp [5]-based completion engine for C# +and an omnifunc-based completer that uses data from Vim's omnicomplete system +to provide semantic completions for many other languages (Ruby, PHP etc.). - Image: YouCompleteMe GIF demo (see reference [5]) + Image: YouCompleteMe GIF demo (see reference [6]) Here's an explanation of what happens in the short GIF demo above. @@ -113,7 +118,7 @@ typing to further filter out unwanted completions. A critical thing to notice is that the completion **filtering is NOT based on the input being a string prefix of the completion** (but that works too). The -input needs to be a _subsequence [6] match_ of a completion. This is a fancy +input needs to be a _subsequence [7] match_ of a completion. This is a fancy way of saying that any input characters need to be present in a completion string in the order in which they appear in the input. So 'abc' is a subsequence of 'xaybgc', but not of 'xbyxaxxc'. After the filter, a complicated @@ -131,7 +136,7 @@ other languages), the semantic engine is triggered (it can also be triggered with a keyboard shortcut; see the rest of the docs). The last thing that you can see in the demo is YCM's integration with Syntastic -[7] (the little red X that shows up in the left gutter) if you are editing a +[8] (the little red X that shows up in the left gutter) if you are editing a C-family file. As Clang compiles your file and detects warnings or errors, they will be piped to Syntastic for display. You don't need to save your file or press any keyboard shortcut to trigger this, it "just happens" in the @@ -150,7 +155,7 @@ languages & Python. Expect more IDE features powered by the various YCM semantic engines in the future. You'll also find that YCM has filepath completers (try typing './' in a file) -and a completer that integrates with UltiSnips [8]. +and a completer that integrates with UltiSnips [9]. =============================================================================== *youcompleteme-mac-os-x-super-quick-installation* @@ -159,16 +164,16 @@ Mac OS X super-quick installation ~ Please refer to the full Installation Guide below; the following commands are provided on a best-effort basis and may not work for you. -Install the latest version of MacVim [9]. Yes, MacVim. And yes, the _latest_. +Install the latest version of MacVim [10]. Yes, MacVim. And yes, the _latest_. If you don't use the MacVim GUI, it is recommended to use the Vim binary that is inside the MacVim.app package ('MacVim.app/Contents/MacOS/Vim'). To ensure -it works correctly copy the 'mvim' script from the MacVim [9] download to your +it works correctly copy the 'mvim' script from the MacVim [10] download to your local binary folder (for example '/usr/local/bin/mvim') and then symlink it: > ln -s /usr/local/bin/mvim vim < -Install YouCompleteMe with Vundle [10]. +Install YouCompleteMe with Vundle [11]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library API has changed (happens rarely), YCM @@ -177,8 +182,8 @@ will notify you to recompile it. You should then rerun the install process. It's recommended that you have the latest Xcode installed along with the latest Command Line Tools (that you install from within Xcode). -Install CMake. Preferably with Homebrew [11], but here's the stand-alone CMake -installer [12]. +Install CMake. Preferably with Homebrew [12], but here's the stand-alone CMake +installer [13]. _If_ you have installed a Homebrew Python and/or Homebrew MacVim, see the _FAQ_ for details. @@ -193,6 +198,9 @@ Compiling YCM **without** semantic support for C-family languages: cd ~/.vim/bundle/YouCompleteMe ./install.sh < +If you want semantic C# support, you should add '--omnisharp-completer' to the +install script as well. + That's it. You're done. Refer to the _User Guide_ section on how to use YCM. Don't forget that if you want the C-family semantic completion engine to work, you will need to provide the compilation flags for your project to YCM. It's @@ -211,9 +219,9 @@ provided on a best-effort basis and may not work for you. Make sure you have Vim 7.3.584 with python2 support. At the time of writing, the version of Vim shipping with Ubuntu is too old. You may need to compile Vim -from source [13] (don't worry, it's easy). +from source [14] (don't worry, it's easy). -Install YouCompleteMe with Vundle [10]. +Install YouCompleteMe with Vundle [11]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library API has changed (happens rarely), YCM @@ -234,6 +242,9 @@ Compiling YCM **without** semantic support for C-family languages: cd ~/.vim/bundle/YouCompleteMe ./install.sh < +If you want semantic C# support, you should add '--omnisharp-completer' to the +install script as well. + That's it. You're done. Refer to the _User Guide_ section on how to use YCM. Don't forget that if you want the C-family semantic completion engine to work, you will need to provide the compilation flags for your project to YCM. It's @@ -248,7 +259,7 @@ that are conservatively turned off by default that you may want to turn on. Windows Installation ~ YCM has **no official support for Windows**, but that doesn't mean you can't -get it to work there. See the Windows Installation Guide [14] wiki page. Feel +get it to work there. See the Windows Installation Guide [15] wiki page. Feel free to add to it. =============================================================================== @@ -278,15 +289,15 @@ will notify you to recompile it. You should then rerun the install process. or higher. If your version of Vim is not recent enough, you may need to compile Vim - from source [13] (don't worry, it's easy). + from source [14] (don't worry, it's easy). After you have made sure that you have Vim 7.3.584+, type the following in Vim: ":echo has('python')". The output should be 1. If it's 0, then get a version of Vim with Python support. -2. **Install YCM** with Vundle [10] (or Pathogen [15], but Vundle is a +2. **Install YCM** with Vundle [11] (or Pathogen [16], but Vundle is a better idea). With Vundle, this would mean adding a "Bundle - 'Valloric/YouCompleteMe'" line to your vimrc [16]. + 'Valloric/YouCompleteMe'" line to your vimrc [17]. 3. [Complete this step ONLY if you care about semantic completion support for C-family languages. Otherwise it's not neccessary.] @@ -294,11 +305,12 @@ will notify you to recompile it. You should then rerun the install process. **Download the latest version of 'libclang'**. Clang is an open-source compiler that can compile C/C++/Objective-C/Objective-C++. The 'libclang' library it provides is used to power the YCM semantic completion engine - for those languages. YCM needs libclang version 3.2 or higher. + for those languages. YCM is designed to work with libclang version 3.3 or + higher, but can in theory work with 3.2 as well. - You can use the system libclang _only if you are sure it is version 3.2 + You can use the system libclang _only if you are sure it is version 3.3 or higher_, otherwise don't. Even if it is, I recommend using the - official binaries from llvm.org [17] if at all possible. Make sure you + official binaries from llvm.org [18] if at all possible. Make sure you download the correct archive file for your OS. 4. **Compile the 'ycm_core' plugin plugin** (ha!) that YCM needs. This is @@ -307,8 +319,8 @@ will notify you to recompile it. You should then rerun the install process. You will need to have 'cmake' installed in order to generate the required makefiles. Linux users can install cmake with their package manager ('sudo apt-get install cmake' for Ubuntu) whereas other users can - download and install [12] cmake from its project site. Mac users can also - get it through Homebrew [11] with 'brew install cmake'. + download and install [13] cmake from its project site. Mac users can also + get it through Homebrew [12] with 'brew install cmake'. You also need to make sure you have Python headers installed. On a Debian-like Linux distro, this would be 'sudo apt-get install python- @@ -326,20 +338,23 @@ will notify you to recompile it. You should then rerun the install process. < Now we need to generate the makefiles. If you DON'T care about semantic support for C-family languages, run the following command in the - 'ycm_build' directory: 'cmake -G "Unix Makefiles" . - ~/.vim/bundle/YouCompleteMe/cpp' - + 'ycm_build' directory: +> + cmake -G "Unix Makefiles" . ~/.vim/bundle/YouCompleteMe/cpp +< If you DO care about semantic support for C-family languages, then your 'cmake' call will be a bit more complicated. We'll assume you downloaded a binary distribution of LLVM+Clang from llvm.org in step 3 and that you extracted the archive file to folder '~/ycm_temp/llvm_root_dir' (with 'bin', 'lib', 'include' etc. folders right inside that folder). With that - in mind, run the following command in the 'ycm_build' directory: 'cmake - -G "Unix Makefiles" -DPATH_TO_LLVM_ROOT=~/ycm_temp/llvm_root_dir . - ~/.vim/bundle/YouCompleteMe/cpp' - - Now that makefiles have been generated, simply run 'make ycm_core'. - + in mind, run the following command in the 'ycm_build' directory: +> + cmake -G "Unix Makefiles" -DPATH_TO_LLVM_ROOT=~/ycm_temp/llvm_root_dir . ~/.vim/bundle/YouCompleteMe/cpp +< + Now that makefiles have been generated, simply run: +> + make ycm_core +< For those who want to use the system version of libclang, you would pass '-DUSE_SYSTEM_LIBCLANG=ON' to cmake _instead of_ the '-DPATH_TO_LLVM_ROOT=...' flag. @@ -430,7 +445,7 @@ General Semantic Completion Engine Usage ~ *youcompleteme-c-family-semantic-completion-engine-usage* C-family Semantic Completion Engine Usage ~ -- You _really_ also want to install the latest version of the Syntastic [7] +- You _really_ also want to install the latest version of the Syntastic [8] Vim plugin. It has support for YCM and together they will provide you with compile errors/warnings practically instantly and without saving the file. @@ -448,14 +463,14 @@ This system was designed this way so that the user can perform any arbitrary sequence of operations to produce a list of compilation flags YCM should hand to Clang. -See YCM's own '.ycm_extra_conf.py' [18] for details on how this works. You +See YCM's own '.ycm_extra_conf.py' [19] for details on how this works. You should be able to use it _as a starting point_. **Don't** just copy/paste that file somewhere and expect things to magically work; **your project needs different flags**. Hint: just replace the strings in the 'flags' variable with compilation flags necessary for your project. That should be enough for 99% of projects. -Yes, Clang's 'CompilationDatabase' system [19] is also supported. Again, see +Yes, Clang's 'CompilationDatabase' system [20] is also supported. Again, see the above linked example file. If Clang encounters errors when compiling the header files that your file @@ -466,7 +481,7 @@ members). This is because Clang fails to build a precompiled preamble for your file if there are any errors in the included headers and that preamble is key to getting fast completions. -Call the ':YcmDiags' command to see if any errors or warnings were detected in +Call the |:YcmDiags| command to see if any errors or warnings were detected in your file. Even better, use Syntastic. ------------------------------------------------------------------------------- @@ -485,6 +500,20 @@ But again, installing YCM with Vundle takes care of all of this for you. In the future expect to see features like go-to-definition for Python as well. +------------------------------------------------------------------------------- + *youcompleteme-c-semantic-completion* +C# semantic completion ~ + +YCM uses OmniSharp [5] to provide semantic completion for C#. It's used as a +git subrepo. If you're installing YCM with Vundle (which is the recommended +way) then Vundle will make sure that the subrepo is checked out when you do +':BundleInstall'. If you're installing YCM by hand, then you need to run 'git +submodule update --init --recursive' when you're checking out the YCM +repository. + +OmniSharp is written in C# and has to be compiled. The 'install.sh' script +takes care of this if you pass '--omnisharp-completer' as an argument. + ------------------------------------------------------------------------------- *youcompleteme-semantic-completion-for-other-languages* Semantic completion for other languages ~ @@ -494,7 +523,7 @@ semantic completions if it does not have a native semantic completion engine for your file's filetype. Vim comes with okayish omnifuncs for various languages like Ruby, PHP etc. It depends on the language. -You can get stellar omnifuncs for Java and Ruby with Eclim [20]. Just make sure +You can get stellar omnifuncs for Java and Ruby with Eclim [21]. Just make sure you have the _latest_ Eclim installed and configured (this means Eclim '>= 2.2.*' and Eclipse '>= 4.2.*'). @@ -512,7 +541,7 @@ Writing New Semantic Completers ~ You have two options here: writing an 'omnifunc' for Vim's omnicomplete system that YCM will then use through its omni-completer, or a custom completer for -YCM using the Completer API [21]. +YCM using the Completer API [22]. Here are the differences between the two approaches: @@ -531,7 +560,7 @@ Here are the differences between the two approaches: than VimScript. If you want to use the 'omnifunc' system, see the relevant Vim docs with ':h -complete-functions'. For the Completer API, see the API docs [21]. +complete-functions'. For the Completer API, see the API docs [22]. If you want to upstream your completer into YCM's source, you should use the Completer API. @@ -540,7 +569,7 @@ Completer API. *youcompleteme-syntastic-integration* Syntastic integration ~ -YCM has explicit support for Syntastic [7] (and vice-versa) if you compiled YCM +YCM has explicit support for Syntastic [8] (and vice-versa) if you compiled YCM with Clang support; this means that any diagnostics (errors or warnings) that Clang encounters while compiling your file will be fed back to Syntastic for display. @@ -562,7 +591,7 @@ can update Vim's GUI after it has finished running. You _have to_ press a key. This will make YCM check for any pending diagnostics updates. You _can_ force a full, blocking compilation cycle with the -':YcmForceCompileAndDiagnostics' command (you may want to map that command to a +|:YcmForceCompileAndDiagnostics| command (you may want to map that command to a key; try putting 'nnoremap :YcmForceCompileAndDiagnostics' in your vimrc). Calling this command will force YCM to immediately recompile your file and display any new diagnostics it encounters. Do note that recompilation with @@ -579,7 +608,7 @@ current file in Vim's 'locationlist', which can be opened with the ':lopen' and ':lclose' commands (make sure you have set 'let g:syntastic_always_populate_loc_list = 1' in your vimrc). A good way to toggle the display of the 'locationlist' with a single key mapping is provided by -another (very small) Vim plugin called ListToggle [22] (which also makes it +another (very small) Vim plugin called ListToggle [23] (which also makes it possible to change the height of the 'locationlist' window), also written by yours truly. @@ -588,7 +617,7 @@ yours truly. Commands ~ ------------------------------------------------------------------------------- -The '*:YcmForceCompileAndDiagnostics*' command +The *:YcmForceCompileAndDiagnostics* command Calling this command will force YCM to immediately recompile your file and display any new diagnostics it encounters. Do note that recompilation with this @@ -598,7 +627,7 @@ You may want to map this command to a key; try putting 'nnoremap :YcmForceCompileAndDiagnostics' in your vimrc. ------------------------------------------------------------------------------- -The '*:YcmDiags*' command +The *:YcmDiags* command Calling this command will fill Vim's 'locationlist' with errors or warnings if any were detected in your file and then open it. @@ -608,20 +637,20 @@ up to date automatically and will also show error/warning notifications in Vim's gutter. ------------------------------------------------------------------------------- -The '*:YcmShowDetailedDiagnostic*' command +The *:YcmShowDetailedDiagnostic* command This command shows the full diagnostic text when the user's cursor is on the line with the diagnostic. ------------------------------------------------------------------------------- -The '*:YcmDebugInfo*' command +The *:YcmDebugInfo* command This will print out various debug information for the current file. Useful to see what compile commands will be used for the file if you're using the semantic completion engine. ------------------------------------------------------------------------------- -The '*:YcmCompleter*' command +The *:YcmCompleter* command This command can be used to invoke completer-specific commands. If the first argument is of the form 'ft=...' the completer for that file type will be used @@ -639,7 +668,7 @@ YcmCompleter subcommands ~ [See the docs for the 'YcmCompleter' command before tackling this section.] The invoked subcommand is automatically routed to the currently active semantic -completer, so ':YcmCompleter GoToDefinition' will invoke the 'GoToDefinition' +completer, so ':YcmCompleter GoToDefinition' will invoke the |GoToDefinition| subcommand on the Python semantic completer if the currently active file is a Python one and on the Clang completer if the currently active file is a C/C++/Objective-C one. @@ -653,14 +682,14 @@ The various 'GoTo*' subcommands add entries to Vim's 'jumplist' so you can use 'CTRL-I' to jump forward; see ':h jumplist' for details). ------------------------------------------------------------------------------- -The '*GoToDeclaration*' subcommand +The *GoToDeclaration* subcommand Looks up the symbol under the cursor and jumps to its declaration. Supported in filetypes: 'c, cpp, objc, objcpp, python' ------------------------------------------------------------------------------- -The '*GoToDefinition*' subcommand +The *GoToDefinition* subcommand Looks up the symbol under the cursor and jumps to its definition. @@ -672,7 +701,7 @@ including with '#include' directives (directly or indirectly) in that file. Supported in filetypes: 'c, cpp, objc, objcpp, python' ------------------------------------------------------------------------------- -The '*GoToDefinitionElseDeclaration*' subcommand +The *GoToDefinitionElseDeclaration* subcommand Looks up the symbol under the cursor and jumps to its definition if possible; if the definition is not accessible from the current translation unit, jumps to @@ -681,7 +710,7 @@ the symbol's declaration. Supported in filetypes: 'c, cpp, objc, objcpp, python' ------------------------------------------------------------------------------- -The '*ClearCompilationFlagCache*' subcommand +The *ClearCompilationFlagCache* subcommand YCM caches the flags it gets from the 'FlagsForFile' function in your 'ycm_extra_conf.py' file if you return them with the 'do_cache' parameter set @@ -699,15 +728,15 @@ Options ~ All options have reasonable defaults so if the plug-in works after installation you don't need to change any options. These options can be configured in your -vimrc script [16] by including a line like this: +vimrc script [17] by including a line like this: > let g:ycm_min_num_of_chars_for_completion = 1 < -Note that after changing an option in your vimrc script [16] you have to +Note that after changing an option in your vimrc script [17] you have to restart Vim for the changes to take effect. ------------------------------------------------------------------------------- -The '*g:ycm_min_num_of_chars_for_completion*' option +The *g:ycm_min_num_of_chars_for_completion* option This option controls the number of characters the user needs to type before identifier-based completion suggestions are triggered. For example, if the @@ -723,7 +752,23 @@ Default: '2' let g:ycm_min_num_of_chars_for_completion = 2 < ------------------------------------------------------------------------------- -The '*g:ycm_filetype_whitelist*' option +The *g:ycm_min_num_identifier_candidate_chars* option + +This option controls the minimum number of characters that a completion +candidate coming from the identifier completer must have to be shown in the +popup menu. + +A special value of '0' means there is no limit. + +NOTE: This option only applies to the identifier completer; it has no effect on +the various semantic completers. + +Default: '0' +> + let g:ycm_min_num_identifier_candidate_chars = 0 +< +------------------------------------------------------------------------------- +The *g:ycm_filetype_whitelist* option This option controls for which Vim filetypes (see ':h filetype') should YCM be turned on. The option value should be a Vim dictionary with keys being filetype @@ -733,7 +778,7 @@ is used like a hash set, meaning that only the keys matter). The '*' key is special and matches all filetypes. By default, the whitelist contains only this '*' key. -YCM also has a 'g:ycm_filetype_blacklist' option that lists filetypes for which +YCM also has a |g:ycm_filetype_blacklist| option that lists filetypes for which YCM shouldn't be turned on. YCM will work only in filetypes that both the whitelist and the blacklist allow (the blacklist "allows" a filetype by _not_ having it as a key). @@ -754,14 +799,14 @@ Default: "{'*' : 1}" let g:ycm_filetype_whitelist = { '*': 1 } < ------------------------------------------------------------------------------- -The '*g:ycm_filetype_blacklist*' option +The *g:ycm_filetype_blacklist* option This option controls for which Vim filetypes (see ':h filetype') should YCM be turned off. The option value should be a Vim dictionary with keys being filetype strings (like 'python', 'cpp' etc) and values being unimportant (the dictionary is used like a hash set, meaning that only the keys matter). -See the 'g:ycm_filetype_whitelist' option for more details on how this works. +See the |g:ycm_filetype_whitelist| option for more details on how this works. Default: "{'notes': 1, 'markdown': 1, 'text': 1}" > @@ -772,7 +817,7 @@ Default: "{'notes': 1, 'markdown': 1, 'text': 1}" \} < ------------------------------------------------------------------------------- -The '*g:ycm_filetype_specific_completion_to_disable*' option +The *g:ycm_filetype_specific_completion_to_disable* option This option controls for which Vim filetypes (see ':h filetype') should the YCM semantic completion engine be turned off. The option value should be a Vim @@ -793,7 +838,7 @@ Default: '{}' let g:ycm_filetype_specific_completion_to_disable = {} < ------------------------------------------------------------------------------- -The '*g:ycm_register_as_syntastic_checker*' option +The *g:ycm_register_as_syntastic_checker* option When set, this option makes YCM register itself as the Syntastic checker for the 'c', 'cpp', 'objc' and 'objcpp' filetypes. This enables the YCM-Syntastic @@ -810,7 +855,7 @@ Default: '1' let g:ycm_register_as_syntastic_checker = 1 < ------------------------------------------------------------------------------- -The '*g:ycm_allow_changing_updatetime*' option +The *g:ycm_allow_changing_updatetime* option When this option is set to '1', YCM will change the 'updatetime' Vim option to '2000' (see ':h updatetime'). This may conflict with some other plugins you @@ -828,7 +873,7 @@ Default: '1' let g:ycm_allow_changing_updatetime = 1 < ------------------------------------------------------------------------------- -The '*g:ycm_complete_in_comments*' option +The *g:ycm_complete_in_comments* option When this option is set to '1', YCM will show the completion menu even when typing inside comments. @@ -838,7 +883,7 @@ Default: '0' let g:ycm_complete_in_comments = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_complete_in_strings*' option +The *g:ycm_complete_in_strings* option When this option is set to '1', YCM will show the completion menu even when typing inside strings. @@ -854,7 +899,7 @@ Default: '1' let g:ycm_complete_in_strings = 1 < ------------------------------------------------------------------------------- -The '*g:ycm_collect_identifiers_from_comments_and_strings*' option +The *g:ycm_collect_identifiers_from_comments_and_strings* option When this option is set to '1', YCM's identifier completer will also collect identifiers from strings and comments. Otherwise, the text in comments and @@ -865,7 +910,7 @@ Default: '0' let g:ycm_collect_identifiers_from_comments_and_strings = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_collect_identifiers_from_tags_files*' option +The *g:ycm_collect_identifiers_from_tags_files* option When this option is set to '1', YCM's identifier completer will also collect identifiers from tags files. The list of tags files to examine is retrieved @@ -874,7 +919,7 @@ from the 'tagfiles()' Vim function which examines the 'tags' Vim option. See YCM will re-index your tags files if it detects that they have been modified. -The only supported tag format is the Exuberant Ctags format [23]. The format +The only supported tag format is the Exuberant Ctags format [24]. The format from "plain" ctags is NOT supported. Ctags needs to be called with the '-- fields=+l' option (that's a lowercase 'L', not a one) because YCM needs the 'language:' field in the tags output. @@ -889,7 +934,7 @@ Default: '0' let g:ycm_collect_identifiers_from_tags_files = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_seed_identifiers_with_syntax*' option +The *g:ycm_seed_identifiers_with_syntax* option When this option is set to '1', YCM's identifier completer will seed its identifier database with the keywords of the programming language you're @@ -904,7 +949,7 @@ Default: '0' let g:ycm_seed_identifiers_with_syntax = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_add_preview_to_completeopt*' option +The *g:ycm_add_preview_to_completeopt* option When this option is set to '1', YCM will add the 'preview' string to Vim's 'completeopt' option (see ':h completeopt'). If your 'completeopt' option @@ -923,24 +968,24 @@ Default: '0' let g:ycm_add_preview_to_completeopt = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_autoclose_preview_window_after_completion*' option +The *g:ycm_autoclose_preview_window_after_completion* option When this option is set to '1', YCM will auto-close the 'preview' window after the user accepts the offered completion string. If there is no 'preview' window triggered because there is no 'preview' string in 'completeopt', this option is -irrelevant. See the 'g:ycm_add_preview_to_completeopt' option for more details. +irrelevant. See the |g:ycm_add_preview_to_completeopt| option for more details. Default: '0' > let g:ycm_autoclose_preview_window_after_completion = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_autoclose_preview_window_after_insertion*' option +The *g:ycm_autoclose_preview_window_after_insertion* option When this option is set to '1', YCM will auto-close the 'preview' window after the user leaves insert mode. This option is irrelevant if -'g:ycm_autoclose_preview_window_after_completion' is set or if no 'preview' -window is triggered. See the 'g:ycm_add_preview_to_completeopt' option for more +|g:ycm_autoclose_preview_window_after_completion| is set or if no 'preview' +window is triggered. See the |g:ycm_add_preview_to_completeopt| option for more details. Default: '0' @@ -948,7 +993,7 @@ Default: '0' let g:ycm_autoclose_preview_window_after_insertion = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_max_diagnostics_to_display*' option +The *g:ycm_max_diagnostics_to_display* option This option controls the maximum number of diagnostics shown to the user when errors or warnings are detected in the file. This option is only relevant if @@ -960,7 +1005,7 @@ Default: '30' let g:ycm_max_diagnostics_to_display = 30 < ------------------------------------------------------------------------------- -The '*g:ycm_key_list_select_completion*' option +The *g:ycm_key_list_select_completion* option This option controls the key mappings used to select the first completion string. Invoking any of them repeatedly cycles forward through the completion @@ -973,7 +1018,7 @@ Default: "['', '']" let g:ycm_key_list_select_completion = ['', ''] < ------------------------------------------------------------------------------- -The '*g:ycm_key_list_previous_completion*' option +The *g:ycm_key_list_previous_completion* option This option controls the key mappings used to select the previous completion string. Invoking any of them repeatedly cycles backwards through the completion @@ -989,7 +1034,7 @@ Default: "['', '']" let g:ycm_key_list_previous_completion = ['', ''] < ------------------------------------------------------------------------------- -The '*g:ycm_key_invoke_completion*' option +The *g:ycm_key_invoke_completion* option This option controls the key mapping used to invoke the completion menu for semantic completion. By default, semantic completion is trigged automatically @@ -1010,11 +1055,11 @@ Default: '' let g:ycm_key_invoke_completion = '' < ------------------------------------------------------------------------------- -The '*g:ycm_key_detailed_diagnostics*' option +The *g:ycm_key_detailed_diagnostics* option This option controls the key mapping used to show the full diagnostic text when the user's cursor is on the line with the diagnostic. It basically calls -':YcmShowDetailedDiagnostic'. +|:YcmShowDetailedDiagnostic|. Setting this option to an empty string will make sure no mapping is created. @@ -1023,7 +1068,7 @@ Default: 'd' let g:ycm_key_detailed_diagnostics = 'd' < ------------------------------------------------------------------------------- -The '*g:ycm_global_ycm_extra_conf*' option +The *g:ycm_global_ycm_extra_conf* option Normally, YCM searches for a '.ycm_extra_conf.py' file for compilation flags (see the User Guide for more details on how this works). This option specifies @@ -1037,7 +1082,7 @@ Default: "''" let g:ycm_global_ycm_extra_conf = '' < ------------------------------------------------------------------------------- -The '*g:ycm_confirm_extra_conf*' option +The *g:ycm_confirm_extra_conf* option When this option is set to '1' YCM will ask once per '.ycm_extra_conf.py' file if it is safe to be loaded. This is to prevent execution of malicious code from @@ -1048,14 +1093,14 @@ Default: '1' let g:ycm_confirm_extra_conf = 1 < ------------------------------------------------------------------------------- -The '*g:ycm_extra_conf_globlist*' option +The *g:ycm_extra_conf_globlist* option This option is a list that may contain several globbing patterns. If a pattern starts with a '!' all '.ycm_extra_conf.py' files matching that pattern will be blacklisted, that is they won't be loaded and no confirmation dialog will be shown. If a pattern does not start with a '!' all files matching that pattern will be whitelisted. Note that this option is not used when confirmation is -disabled using 'g:ycm_confirm_extra_conf' and that items earlier in the list +disabled using |g:ycm_confirm_extra_conf| and that items earlier in the list will take precedence over the later ones. Rules: @@ -1083,7 +1128,7 @@ Default: '[]' let g:ycm_extra_conf_globlist = [] < ------------------------------------------------------------------------------- -The '*g:ycm_filepath_completion_use_working_dir*' option +The *g:ycm_filepath_completion_use_working_dir* option By default, YCM's filepath completion will interpret relative paths like '../' as being relative to the folder of the file of the currently active buffer. @@ -1095,13 +1140,17 @@ Default: '0' let g:ycm_filepath_completion_use_working_dir = 0 < ------------------------------------------------------------------------------- -The '*g:ycm_semantic_triggers*' option +The *g:ycm_semantic_triggers* option This option controls the character-based triggers for the various semantic completion engines. The option holds a dictionary of key-values, where the keys are Vim's filetype strings delimited by commas and values are lists of strings, where the strings are the triggers. +Setting key-value pairs on the dictionary _adds_ semantic triggers to the +internal default set (listed below). You cannot remove the default triggers, +only add new ones. + A "trigger" is a sequence of one or more characters that trigger semantic completion when typed. For instance, C++ ('cpp' filetype) has '.' listed as a trigger. So when the user types 'foo.', the semantic engine will trigger and @@ -1117,19 +1166,20 @@ Default: '[see next line]' \ 'cpp,objcpp' : ['->', '.', '::'], \ 'perl' : ['->'], \ 'php' : ['->', '::'], - \ 'cs,java,javascript,d,vim,ruby,python,perl6,scala,vb,elixir,go' : ['.'], + \ 'cs,java,javascript,d,vim,python,perl6,scala,vb,elixir,go' : ['.'], + \ 'ruby' : ['.', '::'], \ 'lua' : ['.', ':'], \ 'erlang' : [':'], \ } < ------------------------------------------------------------------------------- -The '*g:ycm_cache_omnifunc*' option +The *g:ycm_cache_omnifunc* option -Some omnicompletion engines do not work well with the YCM cache—in particular, -they might not produce all possible results for a given prefix. By unsetting -this option you can ensure that the omnicompletion engine is requeried on every -keypress. That will ensure all completions will be presented, but might cause -stuttering and lagginess if the omnifunc is slow. +Some omnicompletion engines do not work well with the YCM cache—in +particular, they might not produce all possible results for a given prefix. By +unsetting this option you can ensure that the omnicompletion engine is +requeried on every keypress. That will ensure all completions will be +presented, but might cause stuttering and lagginess if the omnifunc is slow. Default: '1' > @@ -1140,7 +1190,7 @@ Default: '1' FAQ ~ ------------------------------------------------------------------------------- -I get a linker warning regarding '*libpython*' on Mac when compiling YCM +I get a linker warning regarding *libpython* on Mac when compiling YCM If the warning is "ld: warning: path '/usr/lib/libpython2.7.dylib' following -L not a directory", then feel free to ignore it; it's caused by a limitation of @@ -1159,13 +1209,13 @@ completion so that you can use the information about the parameters and their types to write the function call. If you would like this window to auto-close after you select a completion -string, set the 'g:ycm_autoclose_preview_window_after_completion' option to '1' +string, set the |g:ycm_autoclose_preview_window_after_completion| option to '1' in your 'vimrc' file. Similarly, the -'g:ycm_autoclose_preview_window_after_insertion' option can be set to close the +|g:ycm_autoclose_preview_window_after_insertion| option can be set to close the 'preview' window after leaving insert mode. If you don't want this window to ever show up, add 'set completeopt-=preview' -to your 'vimrc'. Also make sure that the 'g:ycm_add_preview_to_completeopt' +to your 'vimrc'. Also make sure that the |g:ycm_add_preview_to_completeopt| option is set to '0'. ------------------------------------------------------------------------------- @@ -1176,7 +1226,7 @@ In Vim, run ':messages' and carefully read the output. YCM will echo messages to the message log if it encounters problems. It's likely you misconfigured something and YCM is complaining about it. -Also, you may want to run the ':YcmDebugInfo' command; it will make YCM spew +Also, you may want to run the |:YcmDebugInfo| command; it will make YCM spew out various debugging information, including the compile flags for the file if the file is a C-family language file and you have compiled in Clang support. @@ -1195,7 +1245,7 @@ Sometimes it takes much longer to get semantic completions than normal ~ This means that libclang (which YCM uses for C-family semantic completion) failed to pre-compile your file's preamble. In other words, there was an error compiling some of the source code you pulled in through your header files. I -suggest calling the ':YcmDiags' command to see what they were (even better, +suggest calling the |:YcmDiags| command to see what they were (even better, have Syntastic installed and call ':lopen'). Bottom line, if libclang can't pre-compile your file's preamble because there @@ -1212,6 +1262,10 @@ and **not** "Bundle 'Syntastic'". The first command pulls in the latest version of Syntastic from GitHub while the second one pulls in an old version from vim.org. +Because of a Vundle bug [25], make sure you have completely removed everything +in your Vundle bundle directory ('~/.vim/bundle' by default) before switching +from one Syntastic bundle command to the other. + ------------------------------------------------------------------------------- *youcompleteme-ycm-auto-inserts-completion-strings-i-dont-want* YCM auto-inserts completion strings I don't want! ~ @@ -1249,9 +1303,9 @@ produced. See the full installation guide for help. I'm trying to use a Homebrew Vim with YCM and I'm getting segfaults ~ Something (I don't know what) is wrong with the way that Homebrew configures -and builds Vim. I recommend using MacVim [9]. Even if you don't like the MacVim -GUI, you can use the Vim binary that is inside the MacVim.app package (it's -'MacVim.app/Contents/MacOS/Vim') and get the Vim console experience. +and builds Vim. I recommend using MacVim [10]. Even if you don't like the +MacVim GUI, you can use the Vim binary that is inside the MacVim.app package +(it's 'MacVim.app/Contents/MacOS/Vim') and get the Vim console experience. ------------------------------------------------------------------------------- *youcompleteme-i-have-homebrew-python-and-or-macvim-cant-compile-sigabrt-when-starting* @@ -1259,7 +1313,7 @@ I have a Homebrew Python and/or MacVim; can't compile/SIGABRT when starting ~ You should probably run 'brew rm python; brew install python' to get the latest fixes that should make YCM work with such a configuration. Also rebuild Macvim -then. If you still get problems with this, see issue #18 [24] for suggestions. +then. If you still get problems with this, see issue #18 [26] for suggestions. ------------------------------------------------------------------------------- *youcompleteme-vim-segfaults-when-i-use-semantic-completer-in-ruby-files* @@ -1301,6 +1355,24 @@ library to use. You may need to set these flags to something else, but you need to make sure you use the same version of Python that your Vim binary is built against, which is highly likely to be the system's default Python. +------------------------------------------------------------------------------- + *libpython2.7.a-...-relocation-R_X86_64_32* +I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling ~ + +The error is usually encountered when compiling YCM on Centos or RHEL. The full +error looks something like the following: +> + /usr/bin/ld: /usr/local/lib/libpython2.7.a(abstract.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC +< +It's possible to get a slightly different error that's similar to the one +above. Here's the problem and how you solve it: + +Your 'libpython2.7.a' was not compiled with '-fPIC' so it can't be linked into +'ycm_core.so'. Use the '-DPYTHON_LIBRARY=' CMake flag to point it to a '.so' +version of libpython on your machine (for instance, +'-DPYTHON_LIBRARY=/usr/lib/libpython2.7.so'). Naturally, this means you'll have +to go through the full installation guide by hand. + ------------------------------------------------------------------------------- *Vim:-Caught-deadly-signal-SEGV* I get 'Vim: Caught deadly signal SEGV' on Vim startup ~ @@ -1326,8 +1398,8 @@ YCM does not read identifiers from my tags files ~ First, put 'let g:ycm_collect_identifiers_from_tags_files = 1' in your vimrc. -Make sure you are using Exuberant Ctags [25] to produce your tags files since -the only supported tag format is the Exuberant Ctags format [23]. The format +Make sure you are using Exuberant Ctags [27] to produce your tags files since +the only supported tag format is the Exuberant Ctags format [24]. The format from "plain" ctags is NOT supported. The output of 'ctags --version' should list "Exuberant Ctags". @@ -1350,6 +1422,19 @@ YCM keeps you in a 'completefunc' completion mode when you're typing in insert mode and Vim disables '' in completion mode as a "feature." Sadly there's nothing I can do about this. +------------------------------------------------------------------------------- + *youcompleteme-ycm-conflicts-with-ultisnips-tab-key-usage* +YCM conflicts with UltiSnips TAB key usage ~ + +YCM comes with support for UltiSnips (snippet suggestions in the popup menu), +but you'll have to change the UltiSnips mappings. See ':h UltiSnips-triggers' +in Vim for details. You'll probably want to change some/all of the following +options: +> + g:UltiSnipsExpandTrigger + g:UltiSnipsJumpForwardTrigger + g:UltiSnipsJumpBackwardTrigger +< ------------------------------------------------------------------------------- *youcompleteme-why-isnt-ycm-just-written-in-plain-vimscript-ffs* Why isn't YCM just written in plain VimScript, FFS? ~ @@ -1370,7 +1455,7 @@ in the current file and simple prefix-based fitering. *youcompleteme-why-does-ycm-demand-such-recent-version-of-vim* Why does YCM demand such a recent version of Vim? ~ -During YCM's development several show-stopper bugs where encountered in Vim. +During YCM's development several show-stopper bugs were encountered in Vim. Those needed to be fixed upstream (and were). A few months after those bugs were fixed, Vim trunk landed the 'pyeval()' function which improved YCM performance even more since less time was spent serializing and deserializing @@ -1391,15 +1476,28 @@ You'll have to learn to ignore them. It's a shitty "solution", I know. *vim-sub-autoclose* Nasty bugs happen if I have the 'vim-autoclose' plugin installed ~ -Use the delimitMate [26] plugin instead. It does the same thing without +Use the delimitMate [28] plugin instead. It does the same thing without conflicting with YCM. +------------------------------------------------------------------------------- + *youcompleteme-is-there-sort-of-ycm-mailing-list-i-have-questions* +Is there some sort of YCM mailing list? I have questions ~ + +If you have questions about the plugin or need help, please use the ycm-users +[29] mailing list, _don't_ create issues on the tracker. The tracker is for bug +reports and feature requests. + =============================================================================== *youcompleteme-contact* Contact ~ -If you have questions, bug reports, suggestions, etc. please use the issue -tracker [27]. The latest version is available at +If you have questions about the plugin or need help, please use the ycm-users +[29] mailing list. + +If you have bug reports or feature suggestions, please use the issue tracker +[30]. + +The latest version of the plugin is available at http://valloric.github.io/YouCompleteMe/. The author's homepage is http://val.markovic.io. @@ -1408,7 +1506,7 @@ The author's homepage is http://val.markovic.io. *youcompleteme-license* License ~ -This software is licensed under the GPL v3 license [28]. © 2012 Strahinja Val +This software is licensed under the GPL v3 license [31]. Š 2012 Strahinja Val Markovic . =============================================================================== @@ -1419,29 +1517,32 @@ References ~ [2] https://travis-ci.org/Valloric/YouCompleteMe.png?branch=travis [3] http://clang.llvm.org/ [4] https://github.com/davidhalter/jedi -[5] http://i.imgur.com/0OP4ood.gif -[6] http://en.wikipedia.org/wiki/Subsequence -[7] https://github.com/scrooloose/syntastic -[8] https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt -[9] http://code.google.com/p/macvim/#Download -[10] https://github.com/gmarik/vundle#about -[11] http://mxcl.github.com/homebrew/ -[12] http://www.cmake.org/cmake/resources/software.html -[13] https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-from-source -[14] https://github.com/Valloric/YouCompleteMe/wiki/Windows-Installation-Guide -[15] https://github.com/tpope/vim-pathogen#pathogenvim -[16] http://vimhelp.appspot.com/starting.txt.html#vimrc -[17] http://llvm.org/releases/download.html#3.2 -[18] https://github.com/Valloric/YouCompleteMe/blob/master/cpp/ycm/.ycm_extra_conf.py -[19] http://clang.llvm.org/docs/JSONCompilationDatabase.html -[20] http://eclim.org/ -[21] https://github.com/Valloric/YouCompleteMe/blob/master/python/ycm/completers/completer.py -[22] https://github.com/Valloric/ListToggle -[23] http://ctags.sourceforge.net/FORMAT -[24] https://github.com/Valloric/YouCompleteMe/issues/18 -[25] http://ctags.sourceforge.net/ -[26] https://github.com/Raimondi/delimitMate -[27] https://github.com/Valloric/YouCompleteMe/issues?state=open -[28] http://www.gnu.org/copyleft/gpl.html +[5] https://github.com/nosami/OmniSharpServer +[6] http://i.imgur.com/0OP4ood.gif +[7] http://en.wikipedia.org/wiki/Subsequence +[8] https://github.com/scrooloose/syntastic +[9] https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt +[10] http://code.google.com/p/macvim/#Download +[11] https://github.com/gmarik/vundle#about +[12] http://mxcl.github.com/homebrew/ +[13] http://www.cmake.org/cmake/resources/software.html +[14] https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-from-source +[15] https://github.com/Valloric/YouCompleteMe/wiki/Windows-Installation-Guide +[16] https://github.com/tpope/vim-pathogen#pathogenvim +[17] http://vimhelp.appspot.com/starting.txt.html#vimrc +[18] http://llvm.org/releases/download.html#3.3 +[19] https://github.com/Valloric/YouCompleteMe/blob/master/cpp/ycm/.ycm_extra_conf.py +[20] http://clang.llvm.org/docs/JSONCompilationDatabase.html +[21] http://eclim.org/ +[22] https://github.com/Valloric/YouCompleteMe/blob/master/python/ycm/completers/completer.py +[23] https://github.com/Valloric/ListToggle +[24] http://ctags.sourceforge.net/FORMAT +[25] https://github.com/gmarik/vundle/issues/48 +[26] https://github.com/Valloric/YouCompleteMe/issues/18 +[27] http://ctags.sourceforge.net/ +[28] https://github.com/Raimondi/delimitMate +[29] https://groups.google.com/forum/?hl=en#!forum/ycm-users +[30] https://github.com/Valloric/YouCompleteMe/issues?state=open +[31] http://www.gnu.org/copyleft/gpl.html vim: ft=help