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.59
First Submitted: 2014-02-21 19:50
Last Updated: 2020-07-06 08:07

Dependencies (19)

Required by (96)

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 1 2 3 4 5 6 7 8 9 ... Next › Last »

fwalch commented on 2018-02-23 07:16

The mpack error is due to, which has been fixed with lua51-mpack 1.0.7-2. @warp: If you update your packages (and maybe use makepkg -C to build neovim-git), everything should work.

warp commented on 2018-02-23 03:57

@Fandekasp I installed lua-lpeg and libmpack, still getting the error when I try run vim. Tried to rebuild it I get mpack error. Is there a step missing?

Fandekasp commented on 2018-02-23 02:32

@fwalch, I also got the unibilium error, and when trying to rebuild neovim, it first failed asking me to install lua-lpeg, then failed again asking for lua-mpack. Except it is looking for lua53 mpack, which isn't available on aur (only lua51-mpack?). If trying to symlink /usr/lib/lua/5.1/ → /usr/lib/lua/5.3 , it fails again, this time looking for a lua 5.2 mpack O_o

EDIT: Oh, it looked for lua 5.2 and lua 5.3 only because the lua/5.1/ file was broken (missing related Reinstalling lua51-mpack didn't help.

SOLVED:I just needed to install libmpack, then reinstalling neovim-git worked the unibilium error disappeared.

SUMMARY: To fix the unibilium error, run pacman -S lua-lpeg libmpack neovim-git

fwalch commented on 2018-02-22 20:09

swiftgeek: I just rebuilt against unibilium 2.0.0 without problems. If you're still having problems, can you open an issue upstream?

swiftgeek commented on 2018-02-21 23:40

I had to downgrade unibilium to make it work :(

chetgurevitch commented on 2017-08-07 02:11

Duplicate tag issues arise regularly [1] causing builds to fail until the user does a clean build. This can be fixed by running "rm -rf runtime/docs" directly before the cmake generator [2]. For now I've uploaded neovim-git-ninja with that fix and full incremental build support [3].

[1] (most recent commit causing rebuilds to fail)
[2] (commit documenting fix)

chetgurevitch commented on 2017-07-24 02:50

Thanks for the hints, I fixed arch and modified the PKGBUILD to use ninja without relying on the top-level makefile for any step.

fwalch commented on 2017-06-25 16:56

chetgurevitch: Thanks for the hint about LuaJIT, I had missed moving that from makedepends to depends. As for your other changes, it looks like you switched the code to use the top-level Makefile. This Makefile is only intended for developers and should not be used for packaging. Also, see [1] for hints about when to use "arch=(any)".


chetgurevitch commented on 2017-06-25 04:48

Hi, I've been testing some changes to the package. I updated the dependency list to contain luajit [1], switched the build system to ninja for significantly faster (incremental) builds and cut out some bundled deps along with other minor cleanup work. I'd be happy to co-maintain the package if that's alright with you, otherwise I've linked the changes below for you to look over [2].

I've also got an updated version of the official neovim package and lua51-mpack but I'm holding off on contacting Sven for now. The latter required major changes (including splitting the package [3] [4]) which rely on a fix only available on git currently and I'd like to land any changes to the repo packages together. Everything's in that github repo though.


fwalch commented on 2017-05-03 20:37

machfour: Thanks! I updated the PKGBUILD according to your suggestions.