Package Details: neovim-git 0.4.0.r1426.g4ab7bbf3ea-1

Git Clone URL: (read-only, click to copy)
Package Base: neovim-git
Description: Fork of Vim aiming to improve user experience, plugins, and GUIs.
Upstream URL:
Keywords: editor vim
Licenses: custom:neovim
Conflicts: neovim
Provides: neovim=0.4.0.r1426.g4ab7bbf3ea
Submitter: fhahn
Maintainer: fwalch
Last Packager: fwalch
Votes: 206
Popularity: 1.55
First Submitted: 2014-02-21 19:50
Last Updated: 2020-07-06 08:07

Dependencies (19)

Required by (97)

Sources (1)

Pinned Comments

fwalch commented on 2016-07-04 19:52

Please don't flag this package out-of-date just because the version number displayed on AUR seems old. This is normal for VCS packages. As long as building the package works without problems, it isn't necessary to update the PKGBUILD here. makepkg will automatically retrieve the latest version when you build the package locally.

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

willemw commented on 2015-09-26 17:09

1) Dependency check against Neovim's release version ("neovim>=1.0"): OK.
Dependency check against an AUR VCS-package version ("neovim>=$pkgver") ==> ("neovim>=1.0.r10"): does not seem OK to me.
Didn't know that "pkgver=1.0.r10" would satisfy "neovim>=1.0". Sure?
2) To be honest, in one of my packages I also have a 'depends' refer to a VCS-package.
3) pkgver() function should return a string starting with a version number or with an 'r', not with a dummy '0'.

fwalch commented on 2015-09-26 16:31

willemw: Thanks for your comments!

- Conflicts should be detected because of conflicts=(). The pkgver in provides=() is just to eventually be able to handle versioned dependencies. Say after Neovim's 1.0 release, there would be a "neovim" package with pgkver=1.0 and this neovim-git package with pkgver=1.0.r10 (assuming 10 upstream commits after 1.0 release for this example). If something depends on "neovim>=1.0", both "neovim" and "neovim-git" will be able to satisfy that.
- Generally, I agree. However the problem is that there are no non-VCS packages for these dependencies, because there are no (or only outdated) upstream releases. If I just use depends=('libvterm'), when installing this package AUR helpers will complain that there is no libvterm package and abort. So this would be very inconvenient for users.
- Do you mean that pkgver (the variable) is not up-to-date? That's inherent with VCS packages (and the reason for the pkgver() function), as otherwise for each upstream commit I'd need to push an update to the PKGBUILD.

willemw commented on 2015-09-26 16:14

Some useful general remarks, I hope:
- pkgver in provides=("neovim=${pkgver}"), is that correct? Doesn't this mean that conflicts will not be detected when another version is already installed?
- depends/optdepends/makedepends should normally not refer to devel (bzr, git, etc.) names. For example, libtermkey-bzr should define provides=("libtermkey"). Then 'depends' here can refer to libtermkey.
- pkgver() is not up-to-date.

fwalch commented on 2015-09-22 21:21

@rtwo: I can reproduce, but it's not related to the dependencies. Let's continue the discussion in your upstream issue (

@fauno: Neovim depends on unibilium and libtermkey since 2014, so naturally lots of things have changed in the meantime. Please report problems upstream.

fauno commented on 2015-09-22 19:35

hi, i've been trying to upgrade my neovim-git build but since it depends on unibilium, libvterm and libtermkey there's a noticeable lag while exiting insert mode.

it's really annoying because when i hit escape while in insert mode and start typing commands at normal speed, the escape gets "cancelled" and it continues in insert mode. does this happen to anyone else?

my old build didn't depend on these packages and was even faster than vim, but it broke with the ncurses upgrade :(

rtwo commented on 2015-09-22 18:32

I am having a really wired bug that only appears when I build neovim via aur.

nvim -u NONE -c 'set autochdir'

Then type :b<TAB> which results in :bNext (but expected behavior would be :b - with a list of possible completions).

Can someone please confirm?

I am also happy for any suggestions on what might be causing this (wrong deps?) and how I might be able to track this down.

fwalch commented on 2015-09-16 15:10

@lilydjwg: Hmm, I see.. that's a bit tricky. I don't want to introduce a dependency on Python in this package. I will check upstream if this file could possible be moved into the python-neovim package.

lilydjwg commented on 2015-09-16 14:30

Hi, would you compile the Python script /usr/share/nvim/runtime/autoload/provider/ so that after running as root, there won't be a /usr/share/nvim/runtime/autoload/provider/__pycache__/script_host.cpython-34.pyc file pacman doesn't have an record. Use python -m compileall ${pkgdir}/usr/share/nvim/runtime/autoload/provider should work.

fwalch commented on 2015-09-10 16:21

FYI: if you get "nvim: error while loading shared libraries: cannot open shared object file: No such file or directory", this is because you updated jemalloc, and you have to rebuild Neovim to link against the updated version.

fwalch commented on 2015-08-26 10:31

Turns out it was actually the nvim invocation in the PKGBUILD's "check()" function that started causing problems. Updated the PKGBUILD; the flickering should now be gone and pacaur should again be able to install this package.