Package Details: neovim-git 0.4.0.r2116.geee0668818-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.r2116.geee0668818
Submitter: fhahn
Maintainer: fwalch
Last Packager: fwalch
Votes: 212
Popularity: 4.09
First Submitted: 2014-02-21 19:50
Last Updated: 2020-11-03 17:55

Dependencies (20)

Required by (100)

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

1 2 3 4 5 6 ... Next › Last »

joshauc commented on 2021-01-17 08:27

Sorry, I had to look more into this XD so I deleted my previews comment. There was an Issue with _FORTIFY_SOURCE=2 for neovim for Arch since it is the default in the makepkg. From what I understand this is usually good so it should be kept the same for the makepkg, but it is not compatible with neovim so it is disabled in the Cmake file. I think the best way is to pass it as an argument flag to Cmake to silence the warning.

My first comment was wrong since it would force the _FORTIFY_SOURCE=2 so I edit it :), also thanks for maintaining this package.


fwalch commented on 2021-01-09 10:12

@joshauc: Do you perhaps have -D_FORTIFY_SOURCE in your makepkg.conf? You can add the -U_FORTIFY_SOURCE there as well.

joshauc commented on 2021-01-03 14:48

When I build the package with gcc a lot of warning are produced about

<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition

To silence them I have to edit the PKGBUILD and add the following line to the CMAKE configuration:

  cmake -S"${pkgname}" -Bbuild \
        -DCMAKE_BUILD_TYPE=RelWithDebInfo \

Could this be add to the PKGFILE?

The solution was provided in this issue neovim/issues/2557.

coxackie commented on 2020-12-29 10:01

Out of curiosity, does anyone know/have a user repo containing pre-built binaries of this? (Built in Arch, of course.)

fwalch commented on 2020-11-03 17:56

just1602: Added the dependency, thanks.

just1602 commented on 2020-11-03 13:54

The package is failing to build since tree-sitter dependency looks missing :

In file included from /home/goldman/.cache/paru/clone/neovim-git/src/neovim-git/src/nvim/lua/executor.c:40:
/home/goldman/.cache/paru/clone/neovim-git/src/neovim-git/src/nvim/lua/treesitter.h:8:10: fatal error: tree_sitter/api.h: No such file or directory
    8 | #include "tree_sitter/api.h"
      |          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/nvim/CMakeFiles/nvim.dir/build.make:622: src/nvim/auto/lua/executor.c.generated.h] Error 1
make[1]: *** [CMakeFiles/Makefile2:2666: src/nvim/CMakeFiles/nvim.dir/all] Error 2
make: *** [Makefile:171: all] Error 2
==> ERROR: A failure occurred in build().
error: failed to build 'neovim-git-0.4.0.r1426.g4ab7bbf3ea-1':

fwalch commented on 2020-10-22 15:32

@jck: As Scimmia said, can you try setting e.g. MAKEFLAGS="-j<number of CPU cores>" in your makepkg.conf? On a recent system, using Make or Ninja should not really make a difference when compiling Neovim - it should only take a few seconds either way. On an older system of mine, Make actually runs faster than Ninja, so I would keep it unless there is really a significant advantage of using Ninja over Make for compiling Neovim on some systems.

Scimmia commented on 2020-10-21 15:32

@jck, probably because you didn't set the number of jobs in makepkg.conf

jck commented on 2020-10-21 15:18

Could you update the PKGBUILD to use ninja(similar to

This leads to a considerably faster build.

Shatur commented on 2020-07-06 08:28

@fwalch, thank you!