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: 257
Popularity: 1.30
First Submitted: 2014-02-21 19:50 (UTC)
Last Updated: 2024-09-04 00:24 (UTC)

Dependencies (24)

Required by (430)

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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 40 Next › Last »

fwalch commented on 2015-08-24 09:58 (UTC)

@Spyhawk: Well, to be fair, you *can* install this package with plain makepkg -U, yaourt, aura, and packer (didn't test other helpers). So you could also argue that pacaur does something that "nobody" else is doing. But I'll see what I can do.

fwalch commented on 2015-08-18 15:37 (UTC)

@z33ky, NoniusSenior: Neovim is invoked during the installation to generate helptags for :help. Due to upstream changes, this now shows as a brief flickering of the terminal screen. FYI, installing this package currently doesn't work with the latest released version of pacaur. The problem is fixed in pacaur-git.

<deleted-account> commented on 2015-08-18 08:12 (UTC)

I had the same problem as @z33ky, gnome terminal went blank. I did not modify anything.

z33ky commented on 2015-08-13 15:28 (UTC)

My terminal went completely blank for a fraction of a second but returned to normal. It was also near the completion of the build. I have modified the PKGBUILD to use Ninja instead of GNU Make though.

cgirard commented on 2015-08-13 14:56 (UTC)

@slester: yes I have seen that too. Killing the process usually help but I have not been able to understand what was the reason.

fwalch commented on 2015-07-21 10:55 (UTC)

@anatolik: Sorry, forgot to add: It should be possible to switch the dependencies from "luajit lua51-lpeg lua51-messagepack" to "luajit lua52 lua52-lpeg lua52-messagepack lua52-bitop" or "luajit lua lua-lpeg lua-messagepack lua-bitop" (bitop is "built in" in LuaJIT). Since LuaJIT is required anyway, I didn't want to maintain an explicit dependency on an additional Lua.