Package Details: vim-youcompleteme-git r2565.036ad6e9-1

Git Clone URL: (read-only)
Package Base: vim-youcompleteme-git
Description: A code-completion engine for Vim
Upstream URL:
Keywords: completion engine neovim vim ycm
Licenses: GPL3
Groups: vim-plugins
Submitter: thestinger
Maintainer: artafinde
Last Packager: artafinde
Votes: 151
Popularity: 3.98
First Submitted: 2013-02-05 21:32
Last Updated: 2019-11-09 12:49

Sources (17)

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 »

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.

Derin commented on 2019-10-10 08:09

Apparently msbuild-stable ( ) is also a requirement for C# support.

See the Introduction section of Omnisharp-Roslyn's README:

I can at least anecdotally confirm that I was not able to get C# completions working in YCM/Omnisharp (includes programs like VSCode) without msbuild-stable.

I'd recommend adding it to the optdepends

jamesljlster commented on 2019-10-08 07:28

@jamesbrink @szemy @unxusr @Excelsior @dviktor

I found that JDTLS 0.45.0 is missing from "".

Official YCM build script downloads JDTLS from snapshot page.

So I make a quick fix for JDTLS package downloading issue:

From f8458252dbbb9b935e938fd227d84880550a7f80 Mon Sep 17 00:00:00 2001
From: Zheng-Ling Lai <>
Date: Tue, 8 Oct 2019 15:25:58 +0800
Subject: [PATCH] Fix JDTLS package downloading issue

 PKGBUILD | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PKGBUILD b/PKGBUILD
index 05fdc0e..1ec6ee0 100644
@@ -130,7 +130,7 @@ prepare() {

        if [[ "$jdtls_milestone" != "" ]] && [[ "$jdtls_buildstamp" != "" ]]; then
            echo 'JDTLS package version matched. Downloading...'
-           curl -LO${jdtls_milestone}/${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
+           curl -LO${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
            tar xf ${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
            echo 'Mismatched JDTLS version'

dviktor commented on 2019-10-07 19:17

Have the same problem with JDTLS and not in gzip format