Package Details: neovim-git 0.11.0.r711.g7b7c95dac9-1

Git Clone URL: https://aur.archlinux.org/neovim-git.git (read-only, click to copy)
Package Base: neovim-git
Description: Fork of Vim aiming to improve user experience, plugins, and GUIs
Upstream URL: https://neovim.io
Keywords: editor
Licenses: custom:neovim
Conflicts: neovim
Provides: neovim, vim-plugin-runtime
Submitter: fhahn
Maintainer: Farzat (gpanders)
Last Packager: gpanders
Votes: 256
Popularity: 1.56
First Submitted: 2014-02-21 19:50 (UTC)
Last Updated: 2024-09-04 00:24 (UTC)

Required by (433)

Sources (3)

Pinned Comments

fwalch commented on 2016-07-04 19:52 (UTC) (edited on 2016-07-04 19:54 (UTC) by fwalch)

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 .. 40 Next › Last »

jhossbach commented on 2023-04-29 10:02 (UTC) (edited on 2023-04-29 10:02 (UTC) by jhossbach)

@eclairevoyant Can you add lua51-lpeg as a normal dependency instead of a make dependency? Neovim needs it as a shared library in runtime.

chris34241 commented on 2023-04-27 14:46 (UTC)

I'm getting this error when building:

/usr/bin/ld: cannot find -llpeg: No such file or directory

I think it might be related to this commit but I do not know how to fix it. Any ideas?

syyyr commented on 2023-04-20 14:16 (UTC)

upstream issue for the mpack build failure: https://github.com/neovim/neovim/issues/23213

eclairevoyant commented on 2023-04-20 10:20 (UTC)

yeah, normally the way to avoid your current system's packages affecting the build environment is by building in a clean chroot

moreka commented on 2023-04-20 09:00 (UTC) (edited on 2023-04-20 09:05 (UTC) by moreka)

UPDATE: It works now. Had to manually remove lua51-mpack and then reinstall neovim-git. Thanks again.

Thanks for the amazing speed @eclairevoyant. Unfortunately I still get the same error.

eclairevoyant commented on 2023-04-20 08:50 (UTC)

fixed

moreka commented on 2023-04-20 08:12 (UTC) (edited on 2023-04-20 08:13 (UTC) by moreka)

There is a build failure:

/usr/bin/luajit: ...-git/src/neovim/src/nvim/generators/gen_api_dispatch.lua:196: attempt to call field 'encode' (a nil value)

I am guessing it is due to this commit and is related to mpack. Don't know how to fix it, though. Any ideas?

eclairevoyant commented on 2023-03-04 16:18 (UTC)

If you submit an orphan request for a package that's been out of date more than some threshold (I believe 6 months?) then it will automatically get orphaned. Thanks for reaching out.

REmorin commented on 2023-03-04 16:15 (UTC)

@eclairevoyant Thanks!

About the hypothetical package, I was suggesting it before I found out abandoned packages could be adopted so easily; I think it would have some hypothetical differences (more stability of neovim and the aur package, etc.) over the nightly binaries and master, but not substantial enough.

eclairevoyant commented on 2023-03-04 15:00 (UTC)

@REmorin I've orphaned and adopted neovim-nightly-bin, I can fix the issues there.

Regarding your suggested hypothetical package, rule #1 of the AUR is it should be a useful package; is there some substantial difference with using the nightly branch instead of the master branch?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 40 Next › Last »