Package Details: neovim-git 0.4.0.r2972.g3fbff98cf-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.r2972.g3fbff98cf, vim-plugin-runtime
Submitter: fhahn
Maintainer: fwalch
Last Packager: fwalch
Votes: 217
Popularity: 2.21
First Submitted: 2014-02-21 19:50
Last Updated: 2021-03-06 10:42

Dependencies (20)

Required by (205)

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 »

therisen06 commented on 2021-05-03 13:38

Could you please add -DCMAKE_INSTALL_LIBDIR=lib to the cmake arguments? There is a lib64 vs lib conflict on Arch Linux derivatives (see

lmartinez-mirror commented on 2021-04-11 05:54

I noticed this package and neovim don't have any similar vimdoc.hook files for regenerating helptags. Are there any plans to add something like this to the packages, one that covers both /usr/share/vim/vimfiles/doc/ and /usr/share/nvim/runtime/doc/ maybe?

The last trace of discussion regarding this was a comment I dug up.

EDIT: I also think this package should provide neovim=0.5.0 seeing how that's what's actually reported by nvim --version.

fwalch commented on 2021-03-06 10:42

@lmartinez-mirror: Added, thanks!

lmartinez-mirror commented on 2021-02-17 21:59

Since neovim provides vim-plugin-runtime, wouldn't this package, as well? I see that the PKGBUILD also uses vim's plugin directory, so it would make sense to add it.

joshauc commented on 2021-02-12 07:53

This is great. Thanks for your work. Mine wasn't even a fix sorry for the spam.

fwalch commented on 2021-02-11 17:20

@joshauc: I took another look at this, and I think it can/should be fixed upstream. See #13844 and #13920.

joshauc commented on 2021-02-11 07:36

@fwalch Sorry for asking again, but would -DCMAKE_C_FLAGS="-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1"be added to the PKGFILE?

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.