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

Dependencies (24)

Required by (431)

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 .. 22 23 24 25 26 27 28 29 30 31 32 .. 40 Next › Last »

akuntsch commented on 2015-04-06 13:27 (UTC)

I think pacaur doesn't pull the latest version from github, but no idea why. There was an issue on github (https://github.com/neovim/neovim/issues/2189) concerning helptags which is fixed by now, so maybe pacaur pulls a version where it wasn't fixed yet.

olantwin commented on 2015-04-05 15:22 (UTC)

Is anyone experiencing the helptags problem with other AUR helpers? @akuntsch: Any idea what difference building with pacaur could make?

akuntsch commented on 2015-04-04 19:41 (UTC)

@olantwin: Yep. That's what I did and it worked manually. I also use pacaur but didn't think that this would be the problem at first.

olantwin commented on 2015-04-03 13:49 (UTC)

@akuntsch: Does the build succeed when you use makepkg directly? I've had the same problem, but it seems to be because of a helper (pacaur in my case). Have not been able to figure out what could be causing it.

fmoralesc commented on 2015-03-28 16:22 (UTC)

Disregard my last question, it turned out that I had a local version of unibilium at /usr/local/lib/. :/

fwalch commented on 2015-03-27 16:52 (UTC)

@Softwayer: Packages depending on vim (including plugin packages such as vim-nerdtree) won't work with Neovim even if it provides('vim'), since the runtime path and the executable name are different. If you're looking for a plugin manager, I'd recommend https://github.com/junegunn/vim-plug.

Softwayer commented on 2015-03-27 16:45 (UTC)

That’s right — provide doesn’t mean replace, does it? Anyway, there are lots of plugins depending on vim, so it’s required to have it installed just to use these plugins with neovim, which is a bit ridiculous.

moyamo commented on 2015-03-27 14:05 (UTC)

@Softwayer This package doesn't replace vim (in a packaging sense). It installs itself along side the vim distribution. It is quite possible to have both vim and neovim installed.

Softwayer commented on 2015-03-27 10:00 (UTC)

Why doesn’t it provide 'vim'?

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 40 Next › Last »