Package Details: neovim-git 0.10.0.r2536.g55c9e2c96e-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
Last Packager: Farzat
Votes: 256
Popularity: 2.11
First Submitted: 2014-02-21 19:50 (UTC)
Last Updated: 2024-03-11 05:36 (UTC)

Dependencies (17)

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

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'?

fmoralesc commented on 2015-03-27 02:31 (UTC)

The build is failing for me with these errors: https://gist.github.com/fmoralesc/4e08a250c9c6e8174bdb Any ideas?

fwalch commented on 2015-03-20 12:58 (UTC)

Updated the dependencies to new packages ("msgpack-c" is now in "community", changed "libtermkey-git-neovim" to "libtermkey-bzr"). I think first uninstalling "neovim-git" and "msgpack-git-neovim", then re-installing "neovim-git" will avoid conflicts.

dequis commented on 2015-03-19 06:23 (UTC)

FWIW i upgraded this package and got msgpack errors (error: ‘msgpack_object_union’ has no member named ‘f64’) Had to manually upgrade msgpack-git-neovim, since i had an older version of that package which didn't have those symbols

hunterwerlla commented on 2015-03-10 19:58 (UTC)

If you are having an issue with no colors in neovim: https://github.com/neovim/neovim/issues/2019 . TL;DR - set your TERM environment variable to "xterm-256color" or run "TERM=xterm-256color nvim" I hope this helps anyone else having similar problems.

Timothee commented on 2015-03-10 08:12 (UTC)

Hello fwalch, thanks for your works. Can you add https protocol for clone repository in your PKGBUILD ? It's for pass through in bad proxy and firewall... Like this : source=("$pkgname::git://github.com/neovim/neovim.git") ---> source=("$pkgname::git+https://github.com/neovim/neovim.git") Thanks !

fwalch commented on 2015-02-28 17:28 (UTC)

Neovim currently uses a custom version of libvterm, which is packaged as libvterm-git-neovim. Adopted the package and added as dependency. Building the PKGBUILD should work now. FYI, libvterm has been added as a dependency to Neovim as a preparation for builtin terminal emulation [1]. I think I'll replace the *-git-neovim dependencies with "proper" VCS dependencies (msgpack-c-git, libtermkey-bzr, libvterm-bzr) soon. [1] https://github.com/neovim/neovim/pull/2076

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