Package Details: neovim-git 0.1.5.r49.gc6ac4f8-1

Git Clone URL: https://aur.archlinux.org/neovim-git.git (read-only)
Package Base: neovim-git
Description: Fork of Vim aiming to improve user experience, plugins, and GUIs.
Upstream URL: https://neovim.io
Keywords: editor vim
Licenses: custom:neovim
Conflicts: neovim
Provides: neovim=0.1.5.r49.gc6ac4f8
Submitter: fhahn
Maintainer: fwalch
Last Packager: fwalch
Votes: 196
Popularity: 0.682527
First Submitted: 2014-02-21 19:50
Last Updated: 2016-09-01 19:45

Dependencies (17)

Required by (13)

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

Scimmia commented on 2016-08-15 16:40

It's a -git package built from the latest development HEAD. Both common sense and a quick look at the PKGBUILD tell you it's not a release build.

warp commented on 2016-08-15 16:37

Is it set to release build? Why am I getting .nvimlog in $HOME directory?

https://github.com/neovim/neovim/issues/2913

fwalch commented on 2016-08-07 22:30

ludat: The version number follows the guidelines at [1]. *Edit:* Ah, I guess you mean change just the pkgver variable in the PKGBUILD to "latest", since it will be updated by makepkg? While theoretically possible, no other Arch package seems to do it (?), and it's technically an invalid version, so I'd rather just stick with the current Arch practices.

[1] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

ludat commented on 2016-08-07 04:30

should the version be something like `latest`? since the version number doesn't really mean anything now.

linduxed commented on 2016-07-28 07:48

Commenting out the LUA_CPATH and LUA_PATH environment variable setting in my Zsh configuration did indeed help. Thank you!

fwalch commented on 2016-07-28 06:34

linduxed: Something is definitely broken here. LuaJIT should never try to load from /usr/lib/lua/5.3, it can only use Lua 5.1 modules. Try unsetting the LUA_CPATH environment variable (or setting it to /usr/lib/lua/5.1).

In any case, I don't think your problem is related to this package or to Neovim.

linduxed commented on 2016-07-27 23:59

This is the output I get from that command (even after doing a `pacman -S lua51-lpeg`):

$ luajit -e "require('lpeg')"
luajit: error loading module 'lpeg' from file '/usr/lib/lua/5.3/lpeg.so':
/usr/lib/lua/5.3/lpeg.so: undefined symbol: luaL_setfuncs
stack traceback:
[C]: at 0x00452850
[C]: in function 'require'
(command line):1: in main chunk
[C]: at 0x00404750

fwalch commented on 2016-07-27 21:20

linduxed: Hm, works for me.. do you get any error if you execute `luajit -e "require('lpeg')"`? If yes, there seems to be a problem with your Lua installation (maybe try reinstalling lua51-lpeg). If not, could you post your problem upstream at github.com/neovim/neovim? You can ping me with @fwalch.

linduxed commented on 2016-07-27 15:34

I'm currently getting this error when I build with `makepkg -C`:

-- Checking Lua interpreter /usr/bin/luajit
-- [/usr/bin/luajit] The 'lpeg' lua package is required for building Neovim
-- Checking Lua interpreter /usr/bin/lua5.1
-- [/usr/bin/lua5.1] The 'lpeg' lua package is required for building Neovim
-- Checking Lua interpreter /usr/bin/lua5.2
-- [/usr/bin/lua5.2] The 'lpeg' lua package is required for building Neovim
-- Checking Lua interpreter /usr/bin/lua
-- [/usr/bin/lua] The 'mpack' lua package is required for building Neovim
CMake Error at CMakeLists.txt:392 (message):
A suitable Lua interpreter was not found.

`pacman -Qs lua` yields the following: https://gist.github.com/linduxed/6d30fba0d360b123ec4a0fbbd9807405

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.

All comments