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.50
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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 53 Next › Last »

marcin commented on 2019-11-04 23:52 (UTC)

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 (UTC)

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 (UTC) (edited on 2019-10-25 08:07 (UTC) by Universebenzene)

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 (UTC)

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

CountMurphy commented on 2019-10-11 15:13 (UTC)

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

kumala commented on 2019-10-11 13:52 (UTC)

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 (UTC) (edited on 2019-10-10 08:10 (UTC) by Derin)

Apparently msbuild-stable ( https://aur.archlinux.org/packages/msbuild-stable/ ) is also a requirement for C# support.

See the Introduction section of Omnisharp-Roslyn's README: https://github.com/OmniSharp/omnisharp-roslyn

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 (UTC) (edited on 2019-10-08 07:30 (UTC) by jamesljlster)

@jamesbrink @szemy @unxusr @Excelsior @dviktor

I found that JDTLS 0.45.0 is missing from "https://download.eclipse.org/jdtls/milestones/".

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 <jamesljlster@gmail.com>
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
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -130,7 +130,7 @@ prepare() {

        if [[ "$jdtls_milestone" != "" ]] && [[ "$jdtls_buildstamp" != "" ]]; then
            echo 'JDTLS package version matched. Downloading...'
-           curl -LO http://download.eclipse.org/jdtls/milestones/${jdtls_milestone}/${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
+           curl -LO http://download.eclipse.org/jdtls/snapshots/${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
            tar xf ${jdtls_package_name}-${jdtls_milestone}-${jdtls_buildstamp}.tar.gz
        else
            echo 'Mismatched JDTLS version'
-- 
2.23.0

dviktor commented on 2019-10-07 19:17 (UTC)

Have the same problem with JDTLS and not in gzip format

Excelsior commented on 2019-10-07 07:57 (UTC)

Had the same problem. I think it's caused by the incomplete downloaded jdtls packet, probably because the latest jdtls has been updated recently.