diff --git a/doc/youcompleteme.txt b/doc/youcompleteme.txt index 38fe7a2b..d09392d0 100644 --- a/doc/youcompleteme.txt +++ b/doc/youcompleteme.txt @@ -23,26 +23,36 @@ Contents ~ 6. TypeScript |youcompleteme-typescript| 7. JavaScript |youcompleteme-javascript| 8. Rust |youcompleteme-rust| + 9. Java |youcompleteme-java| 7. User Guide |youcompleteme-user-guide| 1. General Usage |youcompleteme-general-usage| 2. Client-Server Architecture |youcompleteme-client-server-architecture| 3. Completion String Ranking |youcompleteme-completion-string-ranking| 4. General Semantic Completion |youcompleteme-general-semantic-completion| 5. C-family Semantic Completion |youcompleteme-c-family-semantic-completion| - 1. Option 1: Use a compilation database [46] |youcompleteme-option-1-use-compilation-database-46| + 1. Option 1: Use a compilation database [49] |youcompleteme-option-1-use-compilation-database-49| 2. Option 2: Provide the flags manually |youcompleteme-option-2-provide-flags-manually| 3. Errors during compilation |youcompleteme-errors-during-compilation| 6. JavaScript Semantic Completion |youcompleteme-javascript-semantic-completion| - 1. Quick start |youcompleteme-quick-start| + 1. JavaScript quick start |youcompleteme-javascript-quick-start| 2. Explanation |youcompleteme-explanation| 3. Tips and tricks |youcompleteme-tips-tricks| 1. Configuring Tern for node support |youcompleteme-configuring-tern-for-node-support| 2. Configuring Tern for requirejs support |youcompleteme-configuring-tern-for-requirejs-support| 7. Rust Semantic Completion |youcompleteme-rust-semantic-completion| 8. Python Semantic Completion |youcompleteme-python-semantic-completion| - 9. Semantic Completion for Other Languages |youcompleteme-semantic-completion-for-other-languages| - 10. Writing New Semantic Completers |youcompleteme-writing-new-semantic-completers| - 11. Diagnostic Display |youcompleteme-diagnostic-display| + 9. Java Semantic Completion |youcompleteme-java-semantic-completion| + 1. Java quick Start |youcompleteme-java-quick-start| + 2. Java Project Files |youcompleteme-java-project-files| + 3. Diagnostic display - Syntastic |youcompleteme-diagnostic-display-syntastic| + 4. Diagnostic display - Eclim |youcompleteme-diagnostic-display-eclim| + 5. Eclipse Projects |youcompleteme-eclipse-projects| + 6. Maven Projects |youcompleteme-maven-projects| + 7. Gradle Projecs |youcompleteme-gradle-projecs| + 8. Troubleshooting |youcompleteme-troubleshooting| + 10. Semantic Completion for Other Languages |youcompleteme-semantic-completion-for-other-languages| + 11. Writing New Semantic Completers |youcompleteme-writing-new-semantic-completers| + 12. Diagnostic Display |youcompleteme-diagnostic-display| 1. Diagnostic Highlighting Groups |youcompleteme-diagnostic-highlighting-groups| 8. Commands |youcompleteme-commands| 1. The |:YcmRestartServer| command @@ -133,41 +143,41 @@ Contents ~ 48. The |g:ycm_disable_for_files_larger_than_kb| option 49. The |g:ycm_python_binary_path| option 13. FAQ |youcompleteme-faq| - 1. I used to be able to 'import vim' in '.ycm_extra_conf.py', but now can't |youcompleteme-i-used-to-be-able-to-import-vim-in-.ycm_extra_conf.py-but-now-cant| - 2. I get 'ImportError' exceptions that mention 'PyInit_ycm_core' or 'initycm_core' |youcompleteme-i-get-importerror-exceptions-that-mention-pyinit_ycm_core-or-initycm_core| - 3. I get a linker warning regarding 'libpython' on Mac when compiling YCM |youcompleteme-i-get-linker-warning-regarding-libpython-on-mac-when-compiling-ycm| + 1. I used to be able to 'import vim' in '.ycm_extra_conf.py', but now can't |import-vim| + 2. I get |ImportError| exceptions that mention 'PyInit_ycm_core' or 'initycm_core' + 3. I get a linker warning regarding |libpython| on Mac when compiling YCM 4. 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| 5. It appears that YCM is not working |youcompleteme-it-appears-that-ycm-is-not-working| 6. Sometimes it takes much longer to get semantic completions than normal |youcompleteme-sometimes-it-takes-much-longer-to-get-semantic-completions-than-normal| 7. YCM auto-inserts completion strings I don't want! |youcompleteme-ycm-auto-inserts-completion-strings-i-dont-want| - 8. I get a 'E227: mapping already exists for ' error when I start Vim |youcompleteme-i-get-e227-mapping-already-exists-for-blah-error-when-i-start-vim| - 9. I get "'GLIBC_2.XX' not found (required by libclang.so)" when starting Vim |youcompleteme-i-get-glibc_2.xx-not-found-when-starting-vim| + 8. I get a 'E227: mapping already exists for ' error when I start Vim |E227:-mapping-already-exists-for-blah| + 9. I get "'GLIBC_2.XX' not found (required by libclang.so)" when starting Vim |GLIBC_2.XX-not-found()| 10. I'm trying to use a Homebrew Vim with YCM and I'm getting segfaults |youcompleteme-im-trying-to-use-homebrew-vim-with-ycm-im-getting-segfaults| 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. I get 'LONG_BIT definition appears wrong for platform' when compiling |youcompleteme-i-get-long_bit-definition-appears-wrong-for-platform-when-compiling| - 13. I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling |youcompleteme-i-get-libpython2.7.a-...-relocation-r_x86_64_32-when-compiling| - 14. I get 'Vim: Caught deadly signal SEGV' on Vim startup |youcompleteme-i-get-vim-caught-deadly-signal-segv-on-vim-startup| - 15. I get 'Fatal Python error: PyThreadState_Get: no current thread' on startup |youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup| - 16. 'install.py' says python must be compiled with '--enable-framework'. Wat? |youcompleteme-install.py-says-python-must-be-compiled-with-enable-framework-.-wat| + 12. I get 'LONG_BIT definition appears wrong for platform' when compiling |LONG_BIT-definition-appears-wrong-for-platform| + 13. I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling |libpython2.7.a-...-relocation-R_X86_64_32| + 14. I get 'Vim: Caught deadly signal SEGV' on Vim startup |Vim:-Caught-deadly-signal-SEGV| + 15. I get 'Fatal Python error: PyThreadState_Get: no current thread' on startup |Fatal-Python-error:-PyThreadState_Get:-no-current-thread| + 16. |install.py| says python must be compiled with '--enable-framework'. Wat? 17. YCM does not read identifiers from my tags files |youcompleteme-ycm-does-not-read-identifiers-from-my-tags-files| - 18. 'CTRL-U' in insert mode does not work while the completion menu is visible |youcompleteme-ctrl-u-in-insert-mode-does-not-work-while-completion-menu-is-visible| + 18. 'CTRL-U' in insert mode does not work while the completion menu is visible |CTRL-sub-U| 19. YCM conflicts with UltiSnips TAB key usage |youcompleteme-ycm-conflicts-with-ultisnips-tab-key-usage| - 20. Snippets added with ':UltiSnipsAddFiletypes' do not appear in the popup menu |youcompleteme-snippets-added-with-ultisnipsaddfiletypes-do-not-appear-in-popup-menu| + 20. Snippets added with |:UltiSnipsAddFiletypes| do not appear in the popup menu 21. Why isn't YCM just written in plain VimScript, FFS? |youcompleteme-why-isnt-ycm-just-written-in-plain-vimscript-ffs| 22. Why does YCM demand such a recent version of Vim? |youcompleteme-why-does-ycm-demand-such-recent-version-of-vim| - 23. Nasty bugs happen if I have the 'vim-autoclose' plugin installed |youcompleteme-nasty-bugs-happen-if-i-have-vim-autoclose-plugin-installed| + 23. Nasty bugs happen if I have the 'vim-autoclose' plugin installed |vim-sub-autoclose| 24. Is there some sort of YCM mailing list? I have questions |youcompleteme-is-there-sort-of-ycm-mailing-list-i-have-questions| 25. I get an internal compiler error when installing |youcompleteme-i-get-an-internal-compiler-error-when-installing| - 26. I get weird errors when I press 'Ctrl-C' in Vim |youcompleteme-i-get-weird-errors-when-i-press-ctrl-c-in-vim| + 26. I get weird errors when I press 'Ctrl-C' in Vim |Ctrl-sub-C| 27. Why did YCM stop using Syntastic for diagnostics display? |youcompleteme-why-did-ycm-stop-using-syntastic-for-diagnostics-display| 28. Completion doesn't work with the C++ standard library headers |youcompleteme-completion-doesnt-work-with-c-standard-library-headers| 29. When I open a JavaScript file, I get an annoying warning about '.tern-project' -file |youcompleteme-when-i-open-javascript-file-i-get-an-annoying-warning-about-.tern-project-file| +file |.tern-sub-project| 30. When I start vim I get a runtime error saying 'R6034 An application has made an -attempt to load the C runtime library incorrectly.' |youcompleteme-when-i-start-vim-i-get-runtime-error-saying-r6034-an-application-has-made-an-attempt-to-load-c-runtime-library-incorrectly.| +attempt to load the C runtime library incorrectly.' |R6034-An-application-has-made-an-attempt-to-load-the-C-runtime-library-incorrectly.| 31. I hear that YCM only supports Python 2, is that true? |youcompleteme-i-hear-that-ycm-only-supports-python-2-is-that-true| 32. On Windows I get "E887: Sorry, this command is disabled, the Python's site -module could not be loaded" |youcompleteme-on-windows-i-get-e887-sorry-this-command-is-disabled-pythons-site-module-could-not-be-loaded| +module could not be loaded" |E887:-Sorry-this-command-is-disabled-the-Python-s-site-module-could-not-be-loaded| 33. I can't complete python packages in a virtual environment. |youcompleteme-i-cant-complete-python-packages-in-virtual-environment.| 34. I want to defer loading of YouCompleteMe until after Vim finishes booting |i-want-to-defer-loading-of-youcompleteme-until-after-vim-finishes-booting| 35. YCM does not shut down when I quit Vim |youcompleteme-ycm-does-not-shut-down-when-i-quit-vim| @@ -190,7 +200,7 @@ Help, Advice, Support ~ Looking for help, advice or support? Having problems getting YCM to work? First carefully read the installation instructions for your OS. We recommend -you use the supplied 'install.py'. +you use the supplied |install.py|. Next check the User Guide section on the semantic completer that you are using. For C/C++/Objective C, you _must_ read this section. @@ -229,6 +239,7 @@ Contents ~ - JavaScript Semantic Completion - Rust Semantic Completion - Python Semantic Completion + - Java Semantic Completion - Semantic Completion for Other Languages - Writing New Semantic Completers - Diagnostic Display @@ -260,29 +271,22 @@ YouCompleteMe is a fast, as-you-type, fuzzy-search code completion engine for Vim. It has several completion engines: - an identifier-based engine that works with every programming language, - - a Clang [11]-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 [12]-based completion engine for Python 2 and 3 (using the JediHTTP [13] wrapper), - - an OmniSharp [14]-based completion engine for C#, - - a combination of Gocode [15] and Godef [16] semantic engines for Go, - - a TSServer [17]-based completion engine for TypeScript, - - a Tern [18]-based completion engine for JavaScript, - - a racer [19]-based completion engine for Rust, - +- a jdt.ls [20]-based experimental completion engine for Java. - 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 [20]) + Image: YouCompleteMe GIF demo (see reference [21]) Here's an explanation of what happens in the short GIF demo above. @@ -301,7 +305,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 [21] match_ of a completion. This is a fancy +input needs to be a _subsequence [22] 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 @@ -320,7 +324,7 @@ with a keyboard shortcut; see the rest of the docs). The last thing that you can see in the demo is YCM's diagnostic display features (the little red X that shows up in the left gutter; inspired by -Syntastic [22]) if you are editing a C-family file. As Clang compiles your file +Syntastic [23]) if you are editing a C-family file. As Clang compiles your file and detects warnings or errors, they will be presented in various ways. You don't need to save your file or press any keyboard shortcut to trigger this, it "just happens" in the background. @@ -349,7 +353,7 @@ summary and the full list of completer subcommands to find out what's available for your favourite languages. You'll also find that YCM has filepath completers (try typing './' in a file) -and a completer that integrates with UltiSnips [23]. +and a completer that integrates with UltiSnips [24]. =============================================================================== *youcompleteme-installation* @@ -359,20 +363,20 @@ Installation ~ *youcompleteme-mac-os-x* Mac OS X ~ -These instructions (using 'install.py') are the quickest way to install +These instructions (using |install.py|) are the quickest way to install YouCompleteMe, however they may not work for everyone. If the following instructions don't work for you, check out the full installation guide. -Install the latest version of MacVim [24]. Yes, MacVim. And yes, the _latest_. +Install the latest version of MacVim [25]. 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 [24] download to your +it works correctly copy the 'mvim' script from the MacVim [25] 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 [25]. +Install YouCompleteMe with Vundle [26]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library APIs have changed (happens rarely), YCM @@ -383,8 +387,8 @@ installed along with the latest Command Line Tools (they are installed automatically when you run 'clang' for the first time, or manually by running 'xcode-select --install') -Install CMake. Preferably with Homebrew [26], but here's the stand-alone CMake -installer [27]. +Install CMake. Preferably with Homebrew [27], but here's the stand-alone CMake +installer [28]. _If_ you have installed a Homebrew Python and/or Homebrew MacVim, see the _FAQ_ for details. @@ -401,21 +405,24 @@ Compiling YCM **without** semantic support for C-family languages: < The following additional language support options are available: -- C# support: install Mono with Homebrew [26] or by downloading the Mono Mac - package [28] and add '--cs-completer' when calling './install.py'. +- C# support: install Mono with Homebrew [27] or by downloading the Mono Mac + package [29] and add '--cs-completer' when calling './install.py'. -- Go support: install Go [29] and add '--go-completer' when calling +- Go support: install Go [30] and add '--go-completer' when calling './install.py'. -- TypeScript support: install Node.js and npm [30] then install the +- TypeScript support: install Node.js and npm [31] then install the TypeScript SDK with 'npm install -g typescript'. -- JavaScript support: install Node.js and npm [30] and add '--js-completer' +- JavaScript support: install Node.js and npm [31] and add '--js-completer' when calling './install.py'. -- Rust support: install Rust [31] and add '--rust-completer' when calling +- Rust support: install Rust [32] and add '--rust-completer' when calling './install.py'. +- Java support: install JDK8 (version 8 required) [33] and add '--java- + completer' when calling './install.py'. + To simply compile with everything enabled, there's a '--all' flag. So, to install with all language features, ensure 'xbuild', 'go', 'tsserver', 'node', 'npm', 'rustc', and 'cargo' tools are installed and in your 'PATH', then simply @@ -437,16 +444,16 @@ that are conservatively turned off by default that you may want to turn on. *youcompleteme-ubuntu-linux-x64* Ubuntu Linux x64 ~ -These instructions (using 'install.py') are the quickest way to install +These instructions (using |install.py|) are the quickest way to install YouCompleteMe, however they may not work for everyone. If the following instructions don't work for you, check out the full installation guide. Make sure you have Vim 7.4.1578 with Python 2 or Python 3 support. Ubuntu 16.04 and later have a Vim that's recent enough. You can see the version of Vim installed by running 'vim --version'. If the version is too old, you may need -to compile Vim from source [32] (don't worry, it's easy). +to compile Vim from source [34] (don't worry, it's easy). -Install YouCompleteMe with Vundle [25]. +Install YouCompleteMe with Vundle [26]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library APIs have changed (happens rarely), YCM @@ -477,21 +484,24 @@ Compiling YCM **without** semantic support for C-family languages: < The following additional language support options are available: -- C# support: install Mono [33] and add '--cs-completer' when calling +- C# support: install Mono [35] and add '--cs-completer' when calling './install.py'. -- Go support: install Go [29] and add '--go-completer' when calling +- Go support: install Go [30] and add '--go-completer' when calling './install.py'. -- TypeScript support: install Node.js and npm [30] then install the +- TypeScript support: install Node.js and npm [31] then install the TypeScript SDK with 'npm install -g typescript'. -- JavaScript support: install Node.js and npm [30] and add '--js-completer' +- JavaScript support: install Node.js and npm [31] and add '--js-completer' when calling './install.py'. -- Rust support: install Rust [31] and add '--rust-completer' when calling +- Rust support: install Rust [32] and add '--rust-completer' when calling './install.py'. +- Java support: install JDK8 (version 8 required) [33] and add '--java- + completer' when calling './install.py'. + To simply compile with everything enabled, there's a '--all' flag. So, to install with all language features, ensure 'xbuild', 'go', 'tsserver', 'node', 'npm', 'rustc', and 'cargo' tools are installed and in your 'PATH', then simply @@ -513,16 +523,16 @@ that are conservatively turned off by default that you may want to turn on. *youcompleteme-fedora-linux-x64* Fedora Linux x64 ~ -These instructions (using 'install.py') are the quickest way to install +These instructions (using |install.py|) are the quickest way to install YouCompleteMe, however they may not work for everyone. If the following instructions don't work for you, check out the full installation guide. Make sure you have Vim 7.4.1578 with Python 2 or Python 3 support. Fedora 21 and later have a Vim that's recent enough. You can see the version of Vim installed by running 'vim --version'. If the version is too old, you may need -to compile Vim from source [32] (don't worry, it's easy). +to compile Vim from source [34] (don't worry, it's easy). -Install YouCompleteMe with Vundle [25]. +Install YouCompleteMe with Vundle [26]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library APIs have changed (happens rarely), YCM @@ -548,21 +558,24 @@ Compiling YCM **without** semantic support for C-family languages: < The following additional language support options are available: -- C# support: install Mono [34] and add '--cs-completer' when calling +- C# support: install Mono [36] and add '--cs-completer' when calling './install.py'. -- Go support: install Go [29] and add '--go-completer' when calling +- Go support: install Go [30] and add '--go-completer' when calling './install.py'. -- TypeScript support: install Node.js and npm [30] then install the +- TypeScript support: install Node.js and npm [31] then install the TypeScript SDK with 'npm install -g typescript'. -- JavaScript support: install Node.js and npm [30] and add '--js-completer' +- JavaScript support: install Node.js and npm [31] and add '--js-completer' when calling './install.py'. -- Rust support: install Rust [31] and add '--rust-completer' when calling +- Rust support: install Rust [32] and add '--rust-completer' when calling './install.py'. +- Java support: install JDK8 (version 8 required) [33] and add '--java- + completer' when calling './install.py'. + To simply compile with everything enabled, there's a '--all' flag. So, to install with all language features, ensure 'xbuild', 'go', 'tsserver', 'node', 'npm', 'rustc', and 'cargo' tools are installed and in your 'PATH', then simply @@ -584,7 +597,7 @@ that are conservatively turned off by default that you may want to turn on. *youcompleteme-windows* Windows ~ -These instructions (using 'install.py') are the quickest way to install +These instructions (using |install.py|) are the quickest way to install YouCompleteMe, however they may not work for everyone. If the following instructions don't work for you, check out the full installation guide. @@ -597,18 +610,18 @@ Vim. Look at the features included: '+python/dyn' for Python 2 and '+python3/dyn' for Python 3. Take note of the Vim architecture, i.e. 32 or 64-bit. It will be important when choosing the Python installer. We recommend using a 64-bit client. Daily updated copies of 32-bit and 64-bit Vim with -Python 2 and Python 3 support [35] are available. +Python 2 and Python 3 support [37] are available. Add the line: > set encoding=utf-8 < -to your vimrc [36] if not already present. This option is required by YCM. Note +to your vimrc [38] if not already present. This option is required by YCM. Note that it does not prevent you from editing a file in another encoding than UTF-8. You can do that by specifying the '|++enc|' argument to the ':e' command. -Install YouCompleteMe with Vundle [25]. +Install YouCompleteMe with Vundle [26]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library APIs have changed (happens rarely), YCM @@ -616,7 +629,7 @@ will notify you to recompile it. You should then rerun the install process. Download and install the following software: -- Python 2 or Python 3 [37]. Be sure to pick the version corresponding to +- Python 2 or Python 3 [39]. Be sure to pick the version corresponding to your Vim architecture. It is _Windows x86_ for a 32-bit Vim and _Windows x86-64_ for a 64-bit Vim. We recommend installing Python 3. Additionally, the version of Python you install must match up exactly with the version of @@ -628,12 +641,12 @@ Download and install the following software: Python 3.5. You'll need one or the other installed, matching the version number exactly. -- CMake [27]. Add CMake executable to the PATH environment variable. +- CMake [28]. Add CMake executable to the PATH environment variable. -- Visual Studio [38]. Download the community edition. During setup, select +- Visual Studio [40]. Download the community edition. During setup, select _Desktop development with C++_ in _Workloads_. -- 7-zip 16.04 or later [39]. Required to build YCM with semantic support for +- 7-zip 16.04 or later [41]. Required to build YCM with semantic support for C-family languages. Compiling YCM **with** semantic support for C-family languages: @@ -648,20 +661,23 @@ Compiling YCM **without** semantic support for C-family languages: < The following additional language support options are available: -- C# support: add '--cs-completer' when calling 'install.py'. Be sure that - the build utility 'msbuild' is in your PATH [40]. +- C# support: add '--cs-completer' when calling |install.py|. Be sure that + the build utility 'msbuild' is in your PATH [42]. -- Go support: install Go [29] and add '--go-completer' when calling - 'install.py'. +- Go support: install Go [30] and add '--go-completer' when calling + |install.py|. -- TypeScript support: install Node.js and npm [30] then install the +- TypeScript support: install Node.js and npm [31] then install the TypeScript SDK with 'npm install -g typescript'. -- JavaScript support: install Node.js and npm [30] and add '--js-completer' - when calling 'install.py'. +- JavaScript support: install Node.js and npm [31] and add '--js-completer' + when calling |install.py|. -- Rust support: install Rust [31] and add '--rust-completer' when calling - 'install.py'. +- Rust support: install Rust [32] and add '--rust-completer' when calling + |install.py|. + +- Java support: install JDK8 (version 8 required) [33] and add '--java- + completer' when calling './install.py'. To simply compile with everything enabled, there's a '--all' flag. So, to install with all language features, ensure 'msbuild', 'go', 'tsserver', 'node', @@ -687,7 +703,7 @@ that are conservatively turned off by default that you may want to turn on. *youcompleteme-freebsd-openbsd* FreeBSD/OpenBSD ~ -These instructions (using 'install.py') are the quickest way to install +These instructions (using |install.py|) are the quickest way to install YouCompleteMe, however they may not work for everyone. If the following instructions don't work for you, check out the full installation guide. @@ -703,7 +719,7 @@ FreeBSD 10.x comes with clang compiler but not the libraries needed to install. pkg install llvm38 boost-all boost-python-libs clang38 export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/llvm38/lib/ < -Install YouCompleteMe with Vundle [25]. +Install YouCompleteMe with Vundle [26]. **Remember:** YCM is a plugin with a compiled component. If you **update** YCM using Vundle and the ycm_core library APIs have changed (happens rarely), YCM @@ -726,18 +742,21 @@ The following additional language support options are available: - C# support: install Mono and add '--cs-completer' when calling './install.py'. -- Go support: install Go [29] and add '--go-completer' when calling +- Go support: install Go [30] and add '--go-completer' when calling './install.py'. -- TypeScript support: install Node.js and npm [30] then install the +- TypeScript support: install Node.js and npm [31] then install the TypeScript SDK with 'npm install -g typescript'. -- JavaScript support: install Node.js and npm [30] and add '--js-completer' +- JavaScript support: install Node.js and npm [31] and add '--js-completer' when calling './install.py'. -- Rust support: install Rust [31] and add '--rust-completer' when calling +- Rust support: install Rust [32] and add '--rust-completer' when calling './install.py'. +- Java support: install JDK8 (version 8 required) [33] and add '--java- + completer' when calling './install.py'. + To simply compile with everything enabled, there's a '--all' flag. So, to install with all language features, ensure 'xbuild', 'go', 'tsserver', 'node', 'npm', and 'cargo' tools are installed and in your 'PATH', then simply run: @@ -785,7 +804,7 @@ will notify you to recompile it. You should then rerun the install process. higher. If your version of Vim is not recent enough, you may need to compile Vim - from source [32] (don't worry, it's easy). + from source [34] (don't worry, it's easy). After you have made sure that you have Vim 7.4.1578+, type the following in Vim: ":echo has('python') || has('python3')". The output should be 1. @@ -795,9 +814,9 @@ will notify you to recompile it. You should then rerun the install process. critical because it must match the Python and the YCM libraries architectures. We recommend using a 64-bit Vim. -2. **Install YCM** with Vundle [25] (or Pathogen [41], but Vundle is a +2. **Install YCM** with Vundle [26] (or Pathogen [43], but Vundle is a better idea). With Vundle, this would mean adding a "Plugin - 'Valloric/YouCompleteMe'" line to your vimrc [36]. + 'Valloric/YouCompleteMe'" line to your vimrc [38]. If you don't install YCM with Vundle, make sure you have run 'git submodule update --init --recursive' after checking out the YCM @@ -814,7 +833,7 @@ will notify you to recompile it. You should then rerun the install process. You can use the system libclang _only if you are sure it is version 3.9 or higher_, otherwise don't. Even if it is, we recommend using the - official binaries from llvm.org [42] if at all possible. Make sure you + official binaries from llvm.org [44] if at all possible. Make sure you download the correct archive file for your OS. We **STRONGLY recommend AGAINST use** of the system libclang instead of @@ -827,17 +846,17 @@ 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 [27] cmake from its project site. Mac users can also - get it through Homebrew [26] with 'brew install cmake'. + download and install [28] cmake from its project site. Mac users can also + get it through Homebrew [27] with 'brew install cmake'. On a Unix OS, you need to make sure you have Python headers installed. On a Debian-like Linux distro, this would be 'sudo apt-get install python- dev python3-dev'. On Mac they should already be present. - On Windows, you need to download and install Python 2 or Python 3 [37]. + On Windows, you need to download and install Python 2 or Python 3 [39]. Pick the version corresponding to your Vim architecture. You will also need Microsoft Visual C++ (MSVC) to build YCM. You can obtain it by - installing Visual Studio [38]. MSVC 12 (Visual Studio 2013), 14 (2015), + installing Visual Studio [40]. MSVC 12 (Visual Studio 2013), 14 (2015), and 15 (2017) are officially supported. Here we'll assume you installed YCM with Vundle. That means that the top- @@ -880,7 +899,7 @@ will notify you to recompile it. You should then rerun the install process. extracted the archive file to folder '~/ycm_temp/llvm_root_dir' (with 'bin', 'lib', 'include' etc. folders right inside that folder). On Windows, you can extract the files from the LLVM+Clang installer using - 7-zip [39]. + 7-zip [41]. **NOTE:** This _only_ works with a _downloaded_ LLVM binary package, not a custom-built LLVM! See docs below for 'EXTERNAL_LIBCLANG_PATH' when @@ -921,31 +940,38 @@ will notify you to recompile it. You should then rerun the install process. 5. Set up support for additional languages, as desired: - - C# support: install Mono on non-Windows platforms [43]. Navigate to + - C# support: install Mono on non-Windows platforms [45]. Navigate to 'YouCompleteMe/third_party/ycmd/third_party/OmniSharpServer' and run msbuild /property:Configuration=Release /property:Platform="Any CPU" /property:TargetFrameworkVersion=v4.5 On Windows, be sure that the build utility 'msbuild' is in your PATH - [40]. + [42]. - - Go support: install Go [29] and add it to your path. Navigate to + - Go support: install Go [30] and add it to your path. Navigate to 'YouCompleteMe/third_party/ycmd/third_party/gocode' and run 'go build'. - TypeScript support: as with the quick installation, simply 'npm install -g typescript' after successfully installing Node.js and npm - [30]. + [31]. - - JavaScript support: install Node.js and npm [30]. Then navigate to + - JavaScript support: install Node.js and npm [31]. Then navigate to 'YouCompleteMe/third_party/ycmd/third_party/tern_runtime' and run 'npm install --production' - - Rust support: install Rust [31]. Navigate to + - Rust support: install Rust [32]. Navigate to 'YouCompleteMe/third_party/ycmd/third_party/racerd' and run 'cargo build --release'. + - Java support: install JDK8 (version 8 required) [33]. Download a + binary release of eclipse.jdt.ls [46] and extract it to 'YouCompleteM + e/third_party/ycmd/third_party/eclipse.jdt.ls/target/repository'. + Note: this approach is not recommended for most users and is + supported only for advanced users and developers of YCM on a best- + efforts basis. Please use |install.py| to enable java support. + 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 @@ -1041,6 +1067,25 @@ Rust ~ - Management of 'racer' server instance - View documentation comments for identifiers (|GetDoc|) +------------------------------------------------------------------------------- + *youcompleteme-java* +Java ~ + +**NOTE**: Java support is currently experimental. Please let us know your +feedback. + +- Semantic auto-completion +- Go to definition (|GoTo|, |GoToDefinition|, and |GoToDeclaration| are + identical) +- Reference finding (|GoToReferences|) +- Real-time diagnostic display +- Renaming symbols ('RefactorRename ') +- View documentation comments for identifiers (|GetDoc|) +- Type information for identifiers (|GetType|) +- Automatically fix certain errors (|FixIt|) +- Detection of java projects +- Management of 'jdt.ls' server instance + =============================================================================== *youcompleteme-user-guide* User Guide ~ @@ -1063,7 +1108,7 @@ General Usage ~ through the completions. Use Shift-TAB to cycle backwards. Note that if you're using console Vim (that is, not Gvim or MacVim) then it's likely that the Shift-TAB binding will not work because the console will not pass - it to Vim. You can remap the keys; see the _Options [44]_ section below. + it to Vim. You can remap the keys; see the _Options [47]_ section below. Knowing a little bit about how YCM works internally will prevent confusion. YCM has several completion engines: an identifier-based completer that collects all @@ -1090,7 +1135,7 @@ and presents the results to you. Client-Server Architecture ~ YCM has a client-server architecture; the Vim part of YCM is only a thin client -that talks to the ycmd HTTP+JSON server [45] that has the vast majority of YCM +that talks to the ycmd HTTP+JSON server [48] that has the vast majority of YCM logic and functionality. The server is started and stopped automatically as you start and stop Vim. @@ -1130,8 +1175,8 @@ analysis. There are 2 methods which can be used to provide compile flags to 'libclang': ------------------------------------------------------------------------------- - *youcompleteme-option-1-use-compilation-database-46* -Option 1: Use a compilation database [46] ~ + *youcompleteme-option-1-use-compilation-database-49* +Option 1: Use a compilation database [49] ~ The easiest way to get YCM to compile your code is to use a compilation database. A compilation database is usually generated by your build system @@ -1139,13 +1184,13 @@ database. A compilation database is usually generated by your build system in your project. For information on how to generate a compilation database, see the clang -documentation [46]. In short: +documentation [49]. In short: - If using CMake, add '-DCMAKE_EXPORT_COMPILE_COMMANDS=ON' when configuring (or add 'set( CMAKE_EXPORT_COMPILE_COMMANDS ON )' to 'CMakeLists.txt') and copy or symlink the generated database to the root of your project. -- If using Ninja, check out the 'compdb' tool ('-t compdb') in its docs [47]. -- If using GNU make, check out Bear [48]. +- If using Ninja, check out the 'compdb' tool ('-t compdb') in its docs [50]. +- If using GNU make, check out Bear [51]. - For other build systems, check out '.ycm_extra_conf.py' below. If no '.ycm_extra_conf.py' is found, and no 'ycm_global_ycm_extra_conf' is @@ -1225,14 +1270,14 @@ libclang for the file 'filename'. That's it! This is actually enough for most projects, but for complex projects it is not uncommon to integrate directly with an existing build system using the full power of the Python language. -For a more elaborate example, see YCM's own '.ycm_extra_conf.py' [49]. You +For a more elaborate example, see YCM's own '.ycm_extra_conf.py' [52]. 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. -You could also consider using YCM-Generator [50] to generate the +You could also consider using YCM-Generator [53] to generate the 'ycm_extra_conf.py' file. ------------------------------------------------------------------------------- @@ -1255,14 +1300,14 @@ your file. JavaScript Semantic Completion ~ ------------------------------------------------------------------------------- - *youcompleteme-quick-start* -Quick start ~ + *youcompleteme-javascript-quick-start* +JavaScript quick start ~ 1. Ensure that you have enabled the JavaScript completer. See the installation guide for details. 2. Create a '.tern-project' file in the root directory of your JavaScript - project, by following the instructions [51] in the Tern [18] + project, by following the instructions [54] in the Tern [18] documentation. 3. Edit a file from your project. @@ -1272,14 +1317,14 @@ Quick start ~ Explanation ~ JavaScript completion is based on Tern [18]. This completion engine requires a -file named '.tern-project' [51] to exist in the current working directory or a +file named '.tern-project' [54] to exist in the current working directory or a directory which is an ancestor of the current working directory when the Tern server is started. YCM starts the Tern server the first time a JavaScript file is edited and uses its directory as the working directory, so the directory of that file at that time needs to be a descendent of the directory containing the '.tern-project' file (or that directory itself). -Alternatively, as described in the Tern documentation [52], a global '.tern- +Alternatively, as described in the Tern documentation [55], a global '.tern- config' file may be used. Multiple Tern servers are not supported. To switch to a different JavaScript @@ -1294,9 +1339,9 @@ Tips and tricks ~ This section contains some advice for configuring '.tern-project' and working with JavaScript files. The canonical reference for correctly configuring Tern -is the Tern documentation [52]. Any issues, improvements, advice, etc. should +is the Tern documentation [55]. Any issues, improvements, advice, etc. should be sought from the Tern [18] project. For example, see the list of tern plugins -[53] for the list of plugins which can be enabled in the 'plugins' section of +[56] for the list of plugins which can be enabled in the 'plugins' section of the '.tern-project' file. ------------------------------------------------------------------------------- @@ -1348,7 +1393,7 @@ Completions and GoTo commands within the current crate and its dependencies should work out of the box with no additional configuration (provided that you built YCM with the '--rust-completer' flag; see the _Installation_ section for details). For semantic analysis inclusive of the standard library, you must -have a local copy of the Rust source code [54]. If using rustup [55], run the +have a local copy of the Rust source code [57]. If using rustup [58], run the following command to download the code: > rustup component add rust-src @@ -1368,7 +1413,7 @@ Completion and GoTo commands work out of the box with no additional configuration. Those features are provided by the jedi [12] library which supports a variety of Python versions (2.6, 2.7, 3.2+) as long as it runs in the corresponding Python interpreter. By default YCM runs jedi [12] with the -same Python interpreter used by the ycmd server [45], so if you would like to +same Python interpreter used by the ycmd server [48], so if you would like to use a different interpreter, use the following option specifying the Python binary to use. For example, to provide Python 3 completion in your project, set: @@ -1387,32 +1432,170 @@ that directory, the first 'python' that YCM will find will be the one in the virtual environment, so jedi [12] will be able to provide completions for every package you have in the virtual environment. +------------------------------------------------------------------------------- + *youcompleteme-java-semantic-completion* +Java Semantic Completion ~ + +**NOTE**: Java support is currently experimental. Please let us know your +feedback. + +------------------------------------------------------------------------------- + *youcompleteme-java-quick-start* +Java quick Start ~ + +1. Ensure that you have enabled the Java completer. See the installation + guide for details. + +2. Create a project file (gradle or maven) file in the root directory of + your Java project, by following the instructions below. + +3. If you previously used Eclim or Syntastic for Java, disable them for + Java. + +4. Edit a Java file from your project. + +------------------------------------------------------------------------------- + *youcompleteme-java-project-files* +Java Project Files ~ + +In order to provide semantic analysis, the Java completion engine requires +knowledge of your project structure. In particular it needs to know the class +path to use, when compiling your code. Fortunately jdt.ls [20] supports eclipse +project files [59], maven projects [60] and gradle projects [61]. + +**NOTE:** Our recommendation is to use either maven or gradle projects. + +------------------------------------------------------------------------------- + *youcompleteme-diagnostic-display-syntastic* +Diagnostic display - Syntastic ~ + +The native support for Java includes YCM's native realtime diagnostics display. +This can conflict with other dianostics plugins like Syntastic, so when +enabling Java support, please **manually disable Syntastic Java diagnostics**. + +Add the following to your 'vimrc': +> + let g:syntastic_java_checkers = [] +< +------------------------------------------------------------------------------- + *youcompleteme-diagnostic-display-eclim* +Diagnostic display - Eclim ~ + +The native support for Java includes YCM's native realtime diagnostics display. +This can conflict with other dianostics plugins like Eclim, so when enabling +Java support, please **manually disable Eclim Java diagnostics**. + +Add the following to your 'vimrc': +> + let g:EclimFileTypeValidate = 0 +< +**NOTE**: We recommend disabling Eclim entirely when editing Java with YCM's +native Java support. This can be done temporarily with ':EclimDisable'. + +------------------------------------------------------------------------------- + *youcompleteme-eclipse-projects* +Eclipse Projects ~ + +Eclipse style projects require two files: .project [59] and .classpath [62]. + +If your project already has these files due to previously being set up within +eclipse, then no setup is required. jdt.ls [20] should load the project just +fine (it's basically eclipse after all). + +However, if not, it is possible (easy in fact) to craft them manually, though +it is not recommended. You're better off using gradle or maven (see below). + +A simple eclipse style project example [63] can be found in the ycmd test dir. +Normally all that is required is to copy these files to the root of your +project and to edit the '.classpath' to add additional libraries, such as: +> + + +< +It may also be necessary to change the directory in which your source files are +located (paths are relative to the .project file itself): +> + +< +**NOTE**: The eclipse project and classpath files are not a public interface +and it is highly recommended to use Maven or Gradle project definitions if you +don't already use eclipse to manage your projects. + +------------------------------------------------------------------------------- + *youcompleteme-maven-projects* +Maven Projects ~ + +Maven needs a file named pom.xml [60] in the root of the project. Once again a +simple pom.xml [64] can be found in ycmd source. + +The format of pom.xml [60] files is way beyond the scope of this document, but +we do recommend using the various tools that can generate them for you, if +you're not familiar with them already. + +------------------------------------------------------------------------------- + *youcompleteme-gradle-projecs* +Gradle Projecs ~ + +Gradle projects require a build.gradle [61]. Again, there is a trivial example +in ycmd's tests [65]. + +The format of build.gradle [61] files is way beyond the scope of this document, +but we do recommend using the various tools that can generate them for you, if +you're not familiar with them already. + +------------------------------------------------------------------------------- + *youcompleteme-troubleshooting* +Troubleshooting ~ + +If you're not getting completions or diagnostics, check the server health: + +- The Java completion engine takes a while to start up and parse your + project. You should be able to see its progress in the command line, and + |:YcmDebugInfo|. Ensure that the following lines are present: +> + -- jdt.ls Java Language Server running + -- jdt.ls Java Language Server Startup Status: Ready +< +- If the above lines don't appear after a few minutes, check the jdt.ls and + ycmd log files using |:YcmToggleLogs|. The jdt.ls log file is called '.log' + (for some reason). + +If you get a message about "classpath is incomplete", then make sure you have +correctly configured the project files. + +If you get messages about unresolved imports, then make sure you have correctly +configured the project files, in particular check that the classpath is set +correctly. + +For anything else, contact us. Java support is experimental at present so we'd +love to hear your feedback! Please do remember to check CONTRIBUTING.md [66] +for the list of diagnostics we'll need. + ------------------------------------------------------------------------------- *youcompleteme-semantic-completion-for-other-languages* Semantic Completion for Other Languages ~ -C-family, C#, Go, JavaScript, Python, Rust, and TypeScript languages are +C-family, C#, Go, Java, JavaScript, Python, Rust, and TypeScript languages are supported natively by YouCompleteMe using the Clang [11], OmniSharp [14], -Gocode [15]/Godef [16], Tern [18], Jedi [12], racer [19], and TSServer [17] -engines, respectively. Check the installation section for instructions to -enable these features if desired. +Gocode [15]/Godef [16], jdt.ls [20], Tern [18], Jedi [12], racer [19], and +TSServer [17] engines, respectively. Check the installation section for +instructions to enable these features if desired. YCM will use your 'omnifunc' (see ':h omnifunc' in Vim) as a source for 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 [56]. Just make sure -you have the _latest_ Eclim installed and configured (this means Eclim '>= -2.2.*' and Eclipse '>= 4.2.*'). +You can get a stellar omnifunc for Ruby with Eclim [67]. Just make sure you +have the _latest_ Eclim installed and configured (this means Eclim '>= 2.2.*' +and Eclipse '>= 4.2.*'). After installing Eclim remember to create a new Eclipse project within your -application by typing ':ProjectCreate -n ruby' (or '-n -java') inside vim and don't forget to have "let g:EclimCompletionMethod = -'omnifunc'" in your vimrc. This will make YCM and Eclim play nice; YCM will use -Eclim's omnifuncs as the data source for semantic completions and provide the -auto-triggering and subsequence-based matching (and other YCM features) on top -of it. +application by typing ':ProjectCreate -n ruby' inside +vim and don't forget to have "let g:EclimCompletionMethod = 'omnifunc'" in your +vimrc. This will make YCM and Eclim play nice; YCM will use Eclim's omnifuncs +as the data source for semantic completions and provide the auto-triggering and +subsequence-based matching (and other YCM features) on top of it. ------------------------------------------------------------------------------- *youcompleteme-writing-new-semantic-completers* @@ -1420,7 +1603,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 [57]. +YCM using the Completer API [68]. Here are the differences between the two approaches: @@ -1439,7 +1622,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 [57]. +complete-functions'. For the Completer API, see the API docs [68]. If you want to upstream your completer into YCM's source, you should use the Completer API. @@ -1491,7 +1674,7 @@ current file in Vim's 'locationlist', which can be opened with the ':lopen' and ':lclose' commands (make sure you have set 'let g:ycm_always_populate_location_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 [58] (which also makes it +another (very small) Vim plugin called ListToggle [69] (which also makes it possible to change the height of the 'locationlist' window), also written by yours truly. @@ -1533,7 +1716,7 @@ Commands ~ ------------------------------------------------------------------------------- The *:YcmRestartServer* command -If the ycmd completion server [45] suddenly stops for some reason, you can +If the ycmd completion server [48] suddenly stops for some reason, you can restart it with this command. ------------------------------------------------------------------------------- @@ -1581,7 +1764,7 @@ semantic completion engine. The *:YcmToggleLogs* command This command presents the list of logfiles created by YCM, the ycmd server -[45], and the semantic engine server for the current filetype, if any. One of +[48], and the semantic engine server for the current filetype, if any. One of these logfiles can be opened in the editor (or closed if already open) by entering the corresponding number or by clicking on it with the mouse. Additionally, this command can take the logfile names as arguments. Use the @@ -1647,7 +1830,7 @@ The *GoToDeclaration* subcommand Looks up the symbol under the cursor and jumps to its declaration. -Supported in filetypes: 'c, cpp, objc, objcpp, cs, go, python, rust' +Supported in filetypes: 'c, cpp, objc, objcpp, cs, go, python, rust, java' ------------------------------------------------------------------------------- The *GoToDefinition* subcommand @@ -1660,7 +1843,7 @@ translation unit consists of the file you are editing and all the files you are including with '#include' directives (directly or indirectly) in that file. Supported in filetypes: 'c, cpp, objc, objcpp, cs, go, javascript, python, -rust, typescript' +rust, typescript, java' ------------------------------------------------------------------------------- The *GoTo* subcommand @@ -1673,7 +1856,7 @@ C/C++/Objective-C, it first tries to look up the current line for a header and jump to it. For C#, implementations are also considered and preferred. Supported in filetypes: 'c, cpp, objc, objcpp, cs, go, javascript, python, -rust' +rust, java' ------------------------------------------------------------------------------- The *GoToImprecise* subcommand @@ -1696,7 +1879,7 @@ This command attempts to find all of the references within the project to the identifier under the cursor and populates the quickfix list with those locations. -Supported in filetypes: 'javascript, python, typescript' +Supported in filetypes: 'javascript, python, typescript, java' ------------------------------------------------------------------------------- The *GoToImplementation* subcommand @@ -1705,7 +1888,7 @@ Looks up the symbol under the cursor and jumps to its implementation (i.e. non- interface). If there are multiple implementations, instead provides a list of implementations to choose from. -Supported in filetypes: 'cs' +Supported in filetypes: 'cs, java' ------------------------------------------------------------------------------- The *GoToImplementationElseDeclaration* subcommand @@ -1737,7 +1920,7 @@ Invoking this command on 's' returns 'std::string => std::basic_string' **NOTE:** Causes re-parsing of the current translation unit. -Supported in filetypes: 'c, cpp, objc, objcpp, javascript, typescript' +Supported in filetypes: 'c, cpp, objc, objcpp, javascript, typescript, java' ------------------------------------------------------------------------------- The *GetTypeImprecise* subcommand @@ -1795,7 +1978,7 @@ under the cursor. Depending on the file type, this includes things like: - etc. Supported in filetypes: 'c, cpp, objc, objcpp, cs, python, typescript, -javascript, rust' +javascript, rust, java' ------------------------------------------------------------------------------- The *GetDocImprecise* subcommand @@ -1847,7 +2030,7 @@ indication). **NOTE:** Causes re-parsing of the current translation unit. -Supported in filetypes: 'c, cpp, objc, objcpp, cs' +Supported in filetypes: 'c, cpp, objc, objcpp, cs, java' ------------------------------------------------------------------------------- *RefactorRename-new-name* @@ -1863,7 +2046,7 @@ files. Rename operations may involve changes to multiple files, which may or may not be open in Vim buffers at the time. YouCompleteMe handles all of this for you. The behavior is described in the following section. -Supported in filetypes: 'javascript' (variables only), 'typescript' +Supported in filetypes: 'javascript' (variables only), 'typescript, java' ------------------------------------------------------------------------------- *youcompleteme-multi-file-refactor* @@ -1919,7 +2102,7 @@ python binary to use to restart the Python semantic engine. > :YcmCompleter RestartServer /usr/bin/python3.4 < -Supported in filetypes: 'cs, go, javascript, python, rust, typescript' +Supported in filetypes: 'cs, go, javascript, python, rust, typescript, java' ------------------------------------------------------------------------------- The *ClearCompilationFlagCache* subcommand @@ -1959,7 +2142,7 @@ For example: call youcompleteme#GetErrorCount() < Both this function and |youcompleteme#GetWarningCount| can be useful when -integrating YCM with other Vim plugins. For example, a lightline [59] user +integrating YCM with other Vim plugins. For example, a lightline [70] user could add a diagnostics section to their statusline which would display the number of errors and warnings. @@ -2023,11 +2206,11 @@ 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 [36] by including a line like this: +vimrc script [38] 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 [36] you have to +Note that after changing an option in your vimrc script [38] you have to restart Vim for the changes to take effect. ------------------------------------------------------------------------------- @@ -2302,13 +2485,13 @@ YCM will not render it. The following filter types are supported: -- "regex": Accepts a string regular expression [60]. This type matches when +- "regex": Accepts a string regular expression [71]. This type matches when the regex (treated as case-insensitive) is found in the diagnostic text. - "level": Accepts a string level, either "warning" or "error." This type matches when the diagnostic has the same level. -**NOTE:** The regex syntax is **NOT** Vim's, it's Python's [60]. +**NOTE:** The regex syntax is **NOT** Vim's, it's Python's [71]. Default: '{}' > @@ -2397,7 +2580,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 [61]. The format +The only supported tag format is the Exuberant Ctags format [72]. 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. @@ -2434,7 +2617,7 @@ handy; it's a way of sending data from Vim to your 'FlagsForFile' function in your '.ycm_extra_conf.py' file. This option is supposed to be a list of VimScript expression strings that are -evaluated for every request to the ycmd server [45] and then passed to your +evaluated for every request to the ycmd server [48] and then passed to your 'FlagsForFile' function as a 'client_data' keyword argument. For instance, if you set this option to "['v:version']", your 'FlagsForFile' @@ -2463,7 +2646,7 @@ YCM will by default search for an appropriate Python interpreter on your system. You can use this option to override that behavior and force the use of a specific interpreter of your choosing. -**NOTE:** This interpreter is only used for the ycmd server [45]. The YCM +**NOTE:** This interpreter is only used for the ycmd server [48]. The YCM client running inside Vim always uses the Python interpreter that's embedded inside Vim. @@ -2474,7 +2657,7 @@ Default: "''" ------------------------------------------------------------------------------- The *g:ycm_keep_logfiles* option -When this option is set to '1', YCM and the ycmd completion server [45] will +When this option is set to '1', YCM and the ycmd completion server [48] will keep the logfiles around after shutting down (they are deleted on shutdown by default). @@ -2487,7 +2670,7 @@ Default: '0' ------------------------------------------------------------------------------- The *g:ycm_log_level* option -The logging level that YCM and the ycmd completion server [45] use. Valid +The logging level that YCM and the ycmd completion server [48] use. Valid values are the following, from most verbose to least verbose: - 'debug' - 'info' - 'warning' - 'error' - 'critical' @@ -2635,7 +2818,7 @@ The *g:ycm_key_list_stop_completion* option This option controls the key mappings used to close the completion menu. This is useful when the menu is blocking the view, when you need to insert the -'' character, or when you want to expand a snippet from UltiSnips [23] and +'' character, or when you want to expand a snippet from UltiSnips [24] and navigate through it. Default: "['']" @@ -2777,7 +2960,7 @@ It's also possible to use a regular expression as a trigger. You have to prefix your trigger with 're!' to signify it's a regex trigger. For instance, 're!\w+\.' would only trigger after the '\w+\.' regex matches. -**NOTE:** The regex syntax is **NOT** Vim's, it's Python's [60]. +**NOTE:** The regex syntax is **NOT** Vim's, it's Python's [71]. Default: '[see next line]' > @@ -2847,7 +3030,7 @@ The *g:ycm_python_binary_path* option This option specifies the Python interpreter to use to run the jedi [12] completion library. Specify the Python interpreter to use to get completions. -By default the Python under which ycmd [45] runs is used (ycmd [45] runs on +By default the Python under which ycmd [48] runs is used (ycmd [48] runs on Python 2.7 or 3.4+). Default: "''" @@ -2862,11 +3045,11 @@ found through the PATH. FAQ ~ ------------------------------------------------------------------------------- -*youcompleteme-i-used-to-be-able-to-import-vim-in-.ycm_extra_conf.py-but-now-cant* + *import-vim* I used to be able to 'import vim' in '.ycm_extra_conf.py', but now can't ~ YCM was rewritten to use a client-server architecture where most of the logic -is in the ycmd server [45]. So the magic 'vim' module you could have previously +is in the ycmd server [48]. So the magic 'vim' module you could have previously imported in your '.ycm_extra_conf.py' files doesn't exist anymore. To be fair, importing the magic 'vim' module in extra conf files was never @@ -2878,9 +3061,7 @@ working by using the |g:ycm_extra_conf_vim_data| option. See the docs on that option for details. ------------------------------------------------------------------------------- -*youcompleteme-i-get-importerror-exceptions-that-mention-pyinit_ycm_core-or-initycm_core* -I get 'ImportError' exceptions that mention 'PyInit_ycm_core' or ~ -'initycm_core' ~ +I get *ImportError* exceptions that mention 'PyInit_ycm_core' or 'initycm_core' These errors are caused by building the YCM native libraries for Python 2 and trying to load them into a Python 3 process (or the other way around). @@ -2899,8 +3080,7 @@ problem. Common values for that option are '/usr/bin/python' and '/usr/bin/python3'. ------------------------------------------------------------------------------- -*youcompleteme-i-get-linker-warning-regarding-libpython-on-mac-when-compiling-ycm* -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 @@ -2937,7 +3117,7 @@ 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 -out various debugging information, including the YCM and ycmd [45] logfile +out various debugging information, including the YCM and ycmd [48] logfile paths and the compile flags for the current file if the file is a C-family language file and you have compiled in Clang support. Logfiles can be opened in the editor using the |:YcmToggleLogs| command. @@ -2971,7 +3151,7 @@ has to explicitly select something. If something is being selected automatically, this means there's a bug or a misconfiguration somewhere. ------------------------------------------------------------------------------- -*youcompleteme-i-get-e227-mapping-already-exists-for-blah-error-when-i-start-vim* + *E227:-mapping-already-exists-for-blah* I get a 'E227: mapping already exists for ' error when I start Vim ~ This means that YCM tried to set up a key mapping but failed because you @@ -2983,7 +3163,7 @@ with your own. Then change that option value to something else so that the conflict goes away. ------------------------------------------------------------------------------- - *youcompleteme-i-get-glibc_2.xx-not-found-when-starting-vim* + *GLIBC_2.XX-not-found()* I get "'GLIBC_2.XX' not found (required by libclang.so)" when starting Vim ~ Your system is too old for the precompiled binaries from llvm.org. Compile @@ -2995,7 +3175,7 @@ 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 [24]. Even if you don't like the +and builds Vim. I recommend using MacVim [25]. 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. @@ -3005,10 +3185,10 @@ 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 [62] for suggestions. +then. If you still get problems with this, see issue #18 [73] for suggestions. ------------------------------------------------------------------------------- -*youcompleteme-i-get-long_bit-definition-appears-wrong-for-platform-when-compiling* + *LONG_BIT-definition-appears-wrong-for-platform* I get 'LONG_BIT definition appears wrong for platform' when compiling ~ Look at the output of your CMake call. There should be a line in it like the @@ -3041,7 +3221,7 @@ 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. ------------------------------------------------------------------------------- - *youcompleteme-i-get-libpython2.7.a-...-relocation-r_x86_64_32-when-compiling* + *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 @@ -3059,7 +3239,7 @@ version of libpython on your machine (for instance, to go through the full installation guide by hand. ------------------------------------------------------------------------------- - *youcompleteme-i-get-vim-caught-deadly-signal-segv-on-vim-startup* + *Vim:-Caught-deadly-signal-SEGV* I get 'Vim: Caught deadly signal SEGV' on Vim startup ~ This can happen on some Linux distros. If you encounter this situation, run Vim @@ -3074,10 +3254,10 @@ you are using a correct 'libclang.so'. We recommend downloading prebuilt binaries from llvm.org. ------------------------------------------------------------------------------- -*youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup* + *Fatal-Python-error:-PyThreadState_Get:-no-current-thread* I get 'Fatal Python error: PyThreadState_Get: no current thread' on startup ~ -This is caused by linking a static version of 'libpython' into ycmd's +This is caused by linking a static version of |libpython| into ycmd's 'ycm_core.so'. This leads to multiple copies of the python interpreter loaded when 'python' loads 'ycmd_core.so' and this messes up python's global state. The details aren't important. @@ -3092,8 +3272,7 @@ achieved as follows (**NOTE:** for Mac, replace '--enable-shared' with pyenv install {version}' ------------------------------------------------------------------------------- -*youcompleteme-install.py-says-python-must-be-compiled-with-enable-framework-.-wat* -'install.py' says python must be compiled with '--enable-framework'. Wat? ~ +*install.py* says python must be compiled with '--enable-framework'. Wat? See the previous answer for how to ensure your python is built to support dynamic modules. @@ -3104,15 +3283,15 @@ 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 [63] to produce your tags files since -the only supported tag format is the Exuberant Ctags format [61]. The format +Make sure you are using Exuberant Ctags [74] to produce your tags files since +the only supported tag format is the Exuberant Ctags format [72]. The format from "plain" ctags is NOT supported. The output of 'ctags --version' should list "Exuberant Ctags". Ctags needs to be called with the '--fields=+l' (that's a lowercase 'L', not a one) option because YCM needs the 'language:' field in the tags output. -**NOTE:** Exuberant Ctags [63] by default sets language tag for '*.h' files as +**NOTE:** Exuberant Ctags [74] by default sets language tag for '*.h' files as 'C++'. If you have C (not C++) project, consider giving parameter '-- langmap=c:.c.h' to ctags to see tags from '*.h' files. @@ -3125,7 +3304,7 @@ buffer, run ':echo tagfiles()' with the relevant buffer active. Note that that function will only list tag files that already exist. ------------------------------------------------------------------------------- -*youcompleteme-ctrl-u-in-insert-mode-does-not-work-while-completion-menu-is-visible* + *CTRL-sub-U* 'CTRL-U' in insert mode does not work while the completion menu is visible ~ YCM uses 'completefunc' completion mode to show suggestions and Vim disables @@ -3145,8 +3324,7 @@ options: g:UltiSnipsJumpBackwardTrigger < ------------------------------------------------------------------------------- -*youcompleteme-snippets-added-with-ultisnipsaddfiletypes-do-not-appear-in-popup-menu* -Snippets added with ':UltiSnipsAddFiletypes' do not appear in the popup menu ~ +Snippets added with *:UltiSnipsAddFiletypes* do not appear in the popup menu For efficiency, YCM only fetches UltiSnips snippets in specific scenarios like visiting a buffer or setting its filetype. You can force YCM to retrieve them @@ -3178,10 +3356,10 @@ YCM needs a version of Vim with the timers feature to achieve full asynchronicity. This feature is available since Vim 7.4.1578. ------------------------------------------------------------------------------- - *youcompleteme-nasty-bugs-happen-if-i-have-vim-autoclose-plugin-installed* + *vim-sub-autoclose* Nasty bugs happen if I have the 'vim-autoclose' plugin installed ~ -Use the delimitMate [64] plugin instead. It does the same thing without +Use the delimitMate [75] plugin instead. It does the same thing without conflicting with YCM. ------------------------------------------------------------------------------- @@ -3189,7 +3367,7 @@ conflicting with YCM. 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 -[65] mailing list, _don't_ create issues on the tracker. The tracker is for bug +[76] mailing list, _don't_ create issues on the tracker. The tracker is for bug reports and feature requests. ------------------------------------------------------------------------------- @@ -3204,7 +3382,7 @@ by setting the 'YCM_CORES' environment variable to '1'. Example: YCM_CORES=1 ./install.py --clang-completer < ------------------------------------------------------------------------------- - *youcompleteme-i-get-weird-errors-when-i-press-ctrl-c-in-vim* + *Ctrl-sub-C* I get weird errors when I press 'Ctrl-C' in Vim ~ _Never_ use 'Ctrl-C' in Vim. @@ -3243,7 +3421,7 @@ mismatch in assumptions causes performance problems since Syntastic code isn't optimized for this use case of constant diagnostic refreshing. Poor support for this use case also led to crash bugs in Vim caused by -Syntastic-Vim interactions (issue #593 [66]) and other problems, like random +Syntastic-Vim interactions (issue #593 [77]) and other problems, like random Vim flickering. Attempts were made to resolve these issues in Syntastic, but ultimately some of them failed (for various reasons). @@ -3279,10 +3457,10 @@ paths, prepend '-isystem' to each individual path and append them all to the list of flags you return from your 'FlagsForFile' function in your '.ycm_extra_conf.py' file. -See issue #303 [67] for details. +See issue #303 [78] for details. ------------------------------------------------------------------------------- -*youcompleteme-when-i-open-javascript-file-i-get-an-annoying-warning-about-.tern-project-file* + *.tern-sub-project* When I open a JavaScript file, I get an annoying warning about '.tern- ~ project' file ~ @@ -3293,12 +3471,12 @@ If this is still really annoying, and you have a good reason not to have a directory and YCM will stop complaining. ------------------------------------------------------------------------------- -*youcompleteme-when-i-start-vim-i-get-runtime-error-saying-r6034-an-application-has-made-an-attempt-to-load-c-runtime-library-incorrectly.* +*R6034-An-application-has-made-an-attempt-to-load-the-C-runtime-library-incorrectly.* When I start vim I get a runtime error saying 'R6034 An application has made ~ an attempt to load the C runtime library incorrectly.' ~ CMake and other things seem to screw up the PATH with their own msvcrXX.dll -versions. [68] Add the following to the very top of your vimrc to remove these +versions. [79] Add the following to the very top of your vimrc to remove these entries from the path. > python << EOF @@ -3323,18 +3501,18 @@ entries from the path. *youcompleteme-i-hear-that-ycm-only-supports-python-2-is-that-true* I hear that YCM only supports Python 2, is that true? ~ -**No.** Both the Vim client and the ycmd server [45] run on Python 2 or 3. If +**No.** Both the Vim client and the ycmd server [48] run on Python 2 or 3. If you work on a Python 3 project, you may need to set |g:ycm_python_binary_path| to the Python interpreter you use for your project to get completions for that version of Python. ------------------------------------------------------------------------------- -*youcompleteme-on-windows-i-get-e887-sorry-this-command-is-disabled-pythons-site-module-could-not-be-loaded* +*E887:-Sorry-this-command-is-disabled-the-Python-s-site-module-could-not-be-loaded* On Windows I get "E887: Sorry, this command is disabled, the Python's site ~ module could not be loaded" ~ If you are running vim on Windows with Python 2.7.11, this is likely caused by -a bug [69]. Follow this workaround [70] or use a different version (Python +a bug [80]. Follow this workaround [81] or use a different version (Python 2.7.12 does not suffer from the bug). ------------------------------------------------------------------------------- @@ -3366,29 +3544,29 @@ In recent versions of Vim, you can install YCM in a folder under *youcompleteme-ycm-does-not-shut-down-when-i-quit-vim* YCM does not shut down when I quit Vim ~ -YCM relies on the 'VimLeave' event to shut down the ycmd server [45]. Some +YCM relies on the 'VimLeave' event to shut down the ycmd server [48]. Some plugins prevent this event from triggering by exiting Vim through an autocommand without using the 'nested' keyword (see ':h autocmd-nested'). One -of these plugins is vim-nerdtree-tabs [71]. You should identify which plugin is +of these plugins is vim-nerdtree-tabs [82]. You should identify which plugin is responsible for the issue and report it to the plugin author. Note that when -this happens, ycmd [45] will automatically shut itself down after 30 minutes. +this happens, ycmd [48] will automatically shut itself down after 30 minutes. =============================================================================== *youcompleteme-contributor-code-of-conduct* Contributor Code of Conduct ~ Please note that this project is released with a Contributor Code of Conduct -[72]. By participating in this project you agree to abide by its terms. +[83]. By participating in this project you agree to abide by its terms. =============================================================================== *youcompleteme-contact* Contact ~ If you have questions about the plugin or need help, please join the Gitter -room [1] or use the ycm-users [65] mailing list. +room [1] or use the ycm-users [76] mailing list. If you have bug reports or feature suggestions, please use the issue tracker -[73]. Before you do, please carefully read CONTRIBUTING.md [74] as this asks +[84]. Before you do, please carefully read CONTRIBUTING.md [66] as this asks for important diagnostics which the team will use to help get you going. The latest version of the plugin is available at @@ -3403,7 +3581,7 @@ YouCompleteMe maintainers directly using the contact details below. *youcompleteme-license* License ~ -This software is licensed under the GPL v3 license [75]. © 2015-2017 +This software is licensed under the GPL v3 license [85]. © 2015-2017 YouCompleteMe contributors =============================================================================== @@ -3429,61 +3607,71 @@ References ~ [17] https://github.com/Microsoft/TypeScript/tree/master/src/server [18] http://ternjs.net [19] https://github.com/phildawes/racer -[20] http://i.imgur.com/0OP4ood.gif -[21] https://en.wikipedia.org/wiki/Subsequence -[22] https://github.com/scrooloose/syntastic -[23] https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt -[24] https://github.com/macvim-dev/macvim/releases -[25] https://github.com/VundleVim/Vundle.vim#about -[26] http://brew.sh -[27] https://cmake.org/download/ -[28] http://www.mono-project.com/docs/getting-started/install/mac/ -[29] https://golang.org/doc/install -[30] https://docs.npmjs.com/getting-started/installing-node -[31] https://www.rust-lang.org/ -[32] https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-from-source -[33] http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives -[34] http://www.mono-project.com/docs/getting-started/install/linux/#centos-7-fedora-19-and-later-and-derivatives -[35] https://bintray.com/micbou/generic/vim -[36] http://vimhelp.appspot.com/starting.txt.html#vimrc -[37] https://www.python.org/downloads/windows/ -[38] https://www.visualstudio.com/downloads/ -[39] http://www.7-zip.org/download.html -[40] http://stackoverflow.com/questions/6319274/how-do-i-run-msbuild-from-the-command-line-using-windows-sdk-7-1 -[41] https://github.com/tpope/vim-pathogen#pathogenvim -[42] http://llvm.org/releases/download.html -[43] http://www.mono-project.com/docs/getting-started/install/ -[44] https://github.com/Valloric/YouCompleteMe#options -[45] https://github.com/Valloric/ycmd -[46] http://clang.llvm.org/docs/JSONCompilationDatabase.html -[47] https://ninja-build.org/manual.html -[48] https://github.com/rizsotto/Bear -[49] https://raw.githubusercontent.com/Valloric/ycmd/3ad0300e94edc13799e8bf7b831de8b57153c5aa/cpp/ycm/.ycm_extra_conf.py -[50] https://github.com/rdnetto/YCM-Generator -[51] http://ternjs.net/doc/manual.html#configuration -[52] http://ternjs.net/doc/manual.html#server -[53] http://ternjs.net/doc/manual.html#plugins -[54] https://www.rust-lang.org/downloads.html -[55] https://www.rustup.rs/ -[56] http://eclim.org/ -[57] https://github.com/Valloric/ycmd/blob/master/ycmd/completers/completer.py -[58] https://github.com/Valloric/ListToggle -[59] https://github.com/itchyny/lightline.vim -[60] https://docs.python.org/2/library/re.html#regular-expression-syntax -[61] http://ctags.sourceforge.net/FORMAT -[62] https://github.com/Valloric/YouCompleteMe/issues/18 -[63] http://ctags.sourceforge.net/ -[64] https://github.com/Raimondi/delimitMate -[65] https://groups.google.com/forum/?hl=en#!forum/ycm-users -[66] https://github.com/Valloric/YouCompleteMe/issues/593 -[67] https://github.com/Valloric/YouCompleteMe/issues/303 -[68] http://stackoverflow.com/questions/14552348/runtime-error-r6034-in-embedded-python-application/34696022 -[69] https://github.com/vim/vim/issues/717 -[70] https://github.com/vim/vim-win32-installer/blob/a27bbdba9bb87fa0e44c8a00d33d46be936822dd/appveyor.bat#L86-L88 -[71] https://github.com/jistr/vim-nerdtree-tabs -[72] https://github.com/Valloric/YouCompleteMe/blob/master/CODE_OF_CONDUCT.md -[73] https://github.com/Valloric/YouCompleteMe/issues?state=open -[74] https://github.com/Valloric/YouCompleteMe/blob/master/CONTRIBUTING.md -[75] http://www.gnu.org/copyleft/gpl.html +[20] https://github.com/eclipse/eclipse.jdt.ls +[21] http://i.imgur.com/0OP4ood.gif +[22] https://en.wikipedia.org/wiki/Subsequence +[23] https://github.com/scrooloose/syntastic +[24] https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt +[25] https://github.com/macvim-dev/macvim/releases +[26] https://github.com/VundleVim/Vundle.vim#about +[27] http://brew.sh +[28] https://cmake.org/download/ +[29] http://www.mono-project.com/docs/getting-started/install/mac/ +[30] https://golang.org/doc/install +[31] https://docs.npmjs.com/getting-started/installing-node +[32] https://www.rust-lang.org/ +[33] http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html +[34] https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-from-source +[35] http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives +[36] http://www.mono-project.com/docs/getting-started/install/linux/#centos-7-fedora-19-and-later-and-derivatives +[37] https://bintray.com/micbou/generic/vim +[38] http://vimhelp.appspot.com/starting.txt.html#vimrc +[39] https://www.python.org/downloads/windows/ +[40] https://www.visualstudio.com/downloads/ +[41] http://www.7-zip.org/download.html +[42] http://stackoverflow.com/questions/6319274/how-do-i-run-msbuild-from-the-command-line-using-windows-sdk-7-1 +[43] https://github.com/tpope/vim-pathogen#pathogenvim +[44] http://llvm.org/releases/download.html +[45] http://www.mono-project.com/docs/getting-started/install/ +[46] http://download.eclipse.org/jdtls/milestones +[47] https://github.com/Valloric/YouCompleteMe#options +[48] https://github.com/Valloric/ycmd +[49] http://clang.llvm.org/docs/JSONCompilationDatabase.html +[50] https://ninja-build.org/manual.html +[51] https://github.com/rizsotto/Bear +[52] https://raw.githubusercontent.com/Valloric/ycmd/3ad0300e94edc13799e8bf7b831de8b57153c5aa/cpp/ycm/.ycm_extra_conf.py +[53] https://github.com/rdnetto/YCM-Generator +[54] http://ternjs.net/doc/manual.html#configuration +[55] http://ternjs.net/doc/manual.html#server +[56] http://ternjs.net/doc/manual.html#plugins +[57] https://www.rust-lang.org/downloads.html +[58] https://www.rustup.rs/ +[59] https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fproject_description_file.html +[60] https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html +[61] https://docs.gradle.org/current/userguide/tutorial_java_projects.html +[62] https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fjdt%2Fcore%2FIClasspathEntry.html +[63] https://github.com/Valloric/ycmd/tree/master/ycmd/tests/java/testdata/simple_eclipse_project +[64] https://github.com/Valloric/ycmd/blob/java-language-server/ycmd/tests/java/testdata/simple_maven_project/pom.xml +[65] https://github.com/Valloric/ycmd/tree/master/ycmd/tests/java/testdata/simple_gradle_project +[66] https://github.com/Valloric/YouCompleteMe/blob/master/CONTRIBUTING.md +[67] http://eclim.org/ +[68] https://github.com/Valloric/ycmd/blob/master/ycmd/completers/completer.py +[69] https://github.com/Valloric/ListToggle +[70] https://github.com/itchyny/lightline.vim +[71] https://docs.python.org/2/library/re.html#regular-expression-syntax +[72] http://ctags.sourceforge.net/FORMAT +[73] https://github.com/Valloric/YouCompleteMe/issues/18 +[74] http://ctags.sourceforge.net/ +[75] https://github.com/Raimondi/delimitMate +[76] https://groups.google.com/forum/?hl=en#!forum/ycm-users +[77] https://github.com/Valloric/YouCompleteMe/issues/593 +[78] https://github.com/Valloric/YouCompleteMe/issues/303 +[79] http://stackoverflow.com/questions/14552348/runtime-error-r6034-in-embedded-python-application/34696022 +[80] https://github.com/vim/vim/issues/717 +[81] https://github.com/vim/vim-win32-installer/blob/a27bbdba9bb87fa0e44c8a00d33d46be936822dd/appveyor.bat#L86-L88 +[82] https://github.com/jistr/vim-nerdtree-tabs +[83] https://github.com/Valloric/YouCompleteMe/blob/master/CODE_OF_CONDUCT.md +[84] https://github.com/Valloric/YouCompleteMe/issues?state=open +[85] http://www.gnu.org/copyleft/gpl.html vim: ft=help