Package Details: neovim-nightly-bin 0.11.0+dev+1860+g877f3b7288-1

Git Clone URL: https://aur.archlinux.org/neovim-nightly-bin.git (read-only, click to copy)
Package Base: neovim-nightly-bin
Description: Fork of Vim aiming to improve user experience, plugins, and GUIs (nightly build)
Upstream URL: https://neovim.io
Keywords: editor neovim nvim terminal vim
Licenses: custom:neovim
Conflicts: neovim
Provides: neovim, vim-plugin-runtime
Submitter: quebin31
Maintainer: boydaihungst
Last Packager: boydaihungst
Votes: 60
Popularity: 2.68
First Submitted: 2020-12-27 19:08 (UTC)
Last Updated: 2025-02-27 18:12 (UTC)

Dependencies (6)

Required by (450)

Sources (4)

Pinned Comments

quebin31 commented on 2021-10-07 15:37 (UTC)

This PKGBUILD uses the current date to refresh the source url, once it's downloaded the pkgver() function should update the version accordingly.

Latest Comments

1 2 3 4 5 6 Next › Last »

boydaihungst commented on 2025-02-27 18:16 (UTC)

@xiota. Thanks. Removed exit

boydaihungst commented on 2025-02-27 12:23 (UTC)

Bump to v0.11

GrzegorzKozub commented on 2025-02-18 06:55 (UTC)

I allowed myself to create a merge request that should fix this package @eclairevoyant

mostafaqanbaryan commented on 2025-02-08 15:36 (UTC)

As said in the previous comment by @GrzegorzKozub, this package doesn't work anymore

GrzegorzKozub commented on 2025-01-29 06:38 (UTC) (edited on 2025-02-18 06:53 (UTC) by GrzegorzKozub)

I think we need to update nvim-linux64.tar.gz to nvim-linux-x86_64.tar.gz and update the checksum logic due to a recent upstream change @eclairevoyant

REmorin commented on 2023-10-03 23:27 (UTC)

@eclairevoyant, I use chaotic-aur, and sometimes I get the "error":

warning: neovim-nightly-bin: local (0.10.0+dev+9afbfb4-1) is newer than chaotic-aur (0.10.0+dev+09a17f9-1)

So I have to manually do pacman -Syu neovim-nightly-bin. Is there a way to change the pkgver string, so this doesn't happen? Like the "count" number before the commit substring?

eclairevoyant commented on 2023-07-14 05:03 (UTC) (edited on 2023-07-20 00:30 (UTC) by eclairevoyant)

@cjquines don't flag OOD unless there's something wrong with the package, also next time read pinned commments

eclairevoyant commented on 2023-03-04 15:46 (UTC)

Adopted and updated.

In the future, please keep in mind that commenting repeatedly that a package is out-of-date will not improve the situation; if you see a package that's out-of-date and not getting the necessary attention, you can reach out to the maintainer separately or file an orphan request.