Package Details: vim-youcompleteme-git r3216.0d855962-1

Git Clone URL: https://aur.archlinux.org/vim-youcompleteme-git.git (read-only, click to copy)
Package Base: vim-youcompleteme-git
Description: A code-completion engine for Vim
Upstream URL: https://ycm-core.github.io/YouCompleteMe/
Keywords: completion engine neovim vim ycm
Licenses: GPL3
Groups: vim-plugins
Submitter: thestinger
Maintainer: artafinde
Last Packager: artafinde
Votes: 170
Popularity: 0.46
First Submitted: 2013-02-05 21:32 (UTC)
Last Updated: 2024-08-19 15:53 (UTC)

Dependencies (19)

Required by (0)

Sources (2)

Pinned Comments

artafinde commented on 2021-04-10 13:03 (UTC)

If you want to use system's abseil set the _use_system_abseil to ON - default is to download from internet during build.

Latest Comments

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 53 Next › Last »

Melon_Bread commented on 2016-04-14 23:46 (UTC)

@yan12152 Your steps worked perfectly on neovim after installing this package

yan12125 commented on 2016-04-13 18:45 (UTC)

Here are my steps: 1. Install neovim and python3-neovim 2. Add the following line to .vimrc (or init.vim in neovim) let g:ycm_python_binary_path = '/usr/bin/python3' 3. Use vim files in neovim: if has('nvim') set runtimepath+=/usr/share/vim/vimfiles endif 4. `$ nvim` and happy completing :D I don't know how to force authentic vim to run with Python 3, though.

whynothugo commented on 2016-04-13 18:34 (UTC)

@yan12125 That's the same link I provided. It does not answer my question which is "Has anyone else had different results [on arch, with arch's vim package]?"

yan12125 commented on 2016-04-13 17:52 (UTC)

@hobarrera https://github.com/Valloric/YouCompleteMe#i-hear-that-ycm-only-supports-python-2-is-that-true

whynothugo commented on 2016-04-13 17:46 (UTC)

Upstream states that this should work with python3 now. Has anyone gotten this packages working out-of-the-box with python3? It seems that for some reason, vim tries to use python2 to run the server, so it fails: https://github.com/Valloric/YouCompleteMe#i-get-importerror-exceptions-that-mention-pyinit_ycm_core-or-initycm_core Has anyone else had different results?

eberan commented on 2016-04-12 17:46 (UTC)

@idiotbox I understand, thank you for posting. It's important that everyone does that when they have issues, whether it's building, packaging, installing, or using. The issue with PGP isn't specifically with you, but a trend. I will look into communicating the requirement to add the key more visibly. We will keep the PGP requirement for the time being. @siosm I appreciate your use-case (actually reading the PKGBUILD), as without doing so, or watching the build process, the key/signature verification doesn't add security. Let's keep the verification for now at least.

idiotbox commented on 2016-04-12 05:30 (UTC) (edited on 2016-04-12 06:49 (UTC) by idiotbox)

@eberan: I apologize. My intent was actually to help. I mistaked the PGP error for a SHA256SUM error. Thanks for the reply.

Siosm commented on 2016-04-12 01:55 (UTC)

@eberan: It's really a shame that people rush to post unhelpful comments without even reading error messages :(. Even though I think the GPG verification does improve security, if you really want to remove it then at least keep it in the PKGBUILD but as a commented line. Those that actually do read PKGBUILDs before building them may uncomment it :).

eberan commented on 2016-04-12 01:32 (UTC)

Considering the gpg requirement is tripping up a lot of people, and doesn't provide a whole lot of security since I, or any maintainer, can just replace that portion of the PKGBUILD script anyway I think I will be removing the signature verification. Since I check the SHA256SUM and signature prior to packaging anyway, I see the key verification as redundant and an annoyance. Any comments are welcome, before I make the change.

eberan commented on 2016-04-12 01:25 (UTC)

@idiotbox you need to add the pgp key to your keychain for verification. Please check http://llvm.org/releases/download.html#3.8.0 to verify the correct fingerprint and run: gpg --recv-keys 0fc3042e345ad05d

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 53 Next › Last »