Package Details: vim-youcompleteme-git r2535.04c35051-6

Git Clone URL: https://aur.archlinux.org/vim-youcompleteme-git.git (read-only)
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: jamesbrink (staletic)
Last Packager: jamesbrink
Votes: 146
Popularity: 0.962701
First Submitted: 2013-02-05 21:32
Last Updated: 2019-07-15 08:24

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 »

marcin commented on 2019-07-23 00:19

@staletic

Its working now. Thank you!

staletic commented on 2019-07-22 13:28

@marcin

That is a network error. Either you have some sort of firewall/proxy messing with you, or thte jdt host is flaky. You can try downloading jdt from here and placing it wherever the package expects it to be.

marcin commented on 2019-07-22 11:05

@jamesbrink

I'm getting following error:

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 37.6M 0 37.6M 0 0 59894 0 --:--:-- 0:10:58 --:--:-- 132k

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-yo

jamesbrink commented on 2019-07-21 20:41

@marcin it is currently building at working we just need to clean it up. Just build it like any other package.

staletic commented on 2019-07-21 09:14

@jamesbrink

You should keep an eye on these two:

TL;DR: We're planning to do something like g:ycm_clangd_binary_path for go, rust and typecript.

@marcin

I haven't tried this package or the neovim alternative, but they should still work. As a YCM maintainer it's much more convenient for me to install YCM locally, outside of pacman. I also have a bad experience with third party YCM packages from a few years ago, but I'm here to change that.


In the ideal world, we'd e able to package ycmd as a python module, in site-packages and YCM in /usr/share/vim/, but we're far from there right now.

marcin commented on 2019-07-21 04:57

Are there any temporary instructions how to install the package till the thing gets fully sorted out?

jamesbrink commented on 2019-07-19 22:15

@staletic this is awesome thank you so much for the info! I will add you as a co-maintainer. Let's get this thing cleaned up!

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.

jamesbrink commented on 2019-07-15 08:26

I have moved omnisearch-roslyn into it's own package and made it an optional dep. This is still a work in progress, and I will likely need more extensive patches specifically for arch in the future. There is a still a lot of cleanup needed on the git submodules as they should all be listed as sources and not pulled in dynamically per Arch packaging guidelines.

jamesbrink commented on 2019-07-15 01:50

Okay, I have added a simple quick and dirty patch to ycmd that will allow this package to use the existing installed toolchains. I have tested this on my existing account and a fresh account in a chroot. Both seemed to have worked fine for me. If this is an acceptable solution we could decide to re-enable rust support by default.