Package Details: vim-youcompleteme-git r2600.d9a9ce47-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: 151
Popularity: 1.12
First Submitted: 2013-02-05 21:32
Last Updated: 2020-01-05 10:58

Pinned Comments

staletic commented on 2019-07-19 13:11

Hello, I'm one of YCM maintainers. I'll be happy to help with packaging YCM.

Regarding git submodules, instead of pulling from git, just purge them and install the dependencies from official repos.

This is the list of direct YCM/ycmd dependencies (let's leave ycmd bundled for now and let's hope this board supports markdown):

  • python-bottle
  • python-jedi
  • python-regex
  • python-waitress
  • python-future
  • python-requests
  • python-frozendict
  • aur/python-requests-futures

As for completers, TSServer can be installed as an optional dependency and YCM will pick it up if there's no TSServer in third_party.

If this package moves to clangd completer over libclang completer, it could be decoupled too, but the user would need to specify the following

let g:ycm_use_clangd = 1
let g:ycm_clangd_binary_path = 'clangd'

Let's fix those before we dive into decoupling all completers.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

KarlWithK commented on 2019-12-04 17:21

@Universebenzene Thanks for the fix.

Universebenzene commented on 2019-12-04 12:04

@KarlWithK Seems that a submodule is missed in the PKGBUILD. Possible fix here: https://github.com/archlinuxcn/repo/commit/360b4605a9ac380676d9279b91f4490b720b7f10#diff-edeecce400204b781ebdbeb2625dd849

KarlWithK commented on 2019-12-04 11:23

Hello, I am having problems with jedi / Python completion. Whenever I try to write a function I get this error: FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/vim/vimfiles/third_party/ycmd/third_party/jedi_deps/jedi/jedi/third_party/typeshed/stdlib'. I am not sure how to fix this or even if this is the right place to ask. Thanks for the help.

artafinde commented on 2019-11-09 12:54

Early warning: upstream is dropping support for python2 hence this PKGBUILD will also drop support for it very soon see github

marcin commented on 2019-11-04 23:52

The workaround for "Parsing out the JDTLS package version from upstream" is to disable java in PKGBUILD when maually building the package. Change _java="y" into _java="n" at the beginning of the file.

MasterMax commented on 2019-10-28 13:23

I am still having the problem with JDTLS: ...

==> Starting prepare()... Parsing out the JDTLS package version from upstream... JDTLS package version matched. Downloading... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 21211 0 21211 0 0 55093 0 --:--:-- --:--:-- --:--:-- 55093

gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now ==> ERROR: A failure occurred in prepare(). Aborting... Error making: vim-youcompleteme-git

Universebenzene commented on 2019-10-25 08:06

The new ycm upstream add the typeshed submodule under jedi, so it should be included while packaging, or there will be errors while using ycm (e.g. completing the python code).

Wrexes commented on 2019-10-15 20:24

Yup, using Yay's --editmenu and fixing the PKGBUILD worked. Thanks @jamesljlster !

CountMurphy commented on 2019-10-11 15:13

follow the advice of staletic and jamesljlster and it will build. PKGBUILD needs updating.

kumala commented on 2019-10-11 13:52

Checking the PKGBUILD I can see the patch from @jamesljlster is present but yet the JDTLS and not in gzip format is also present.