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: 255
Popularity: 2.16
First Submitted: 2014-02-21 19:50 (UTC)
Last Updated: 2024-03-11 05:36 (UTC)

Dependencies (17)

Required by (427)

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

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

Farzat commented on 2024-03-11 05:38 (UTC)

Alright then, I removed the verbose flag.

wsduvall commented on 2024-03-10 14:18 (UTC)

@xiota, I agree, and in the rare case people need to look at problems with the CC/CXX/CFLAGS/CXXFLAGS, they can enable it. I don't think there's a need for all of us to have to see them every time we rebuild.

xiota commented on 2024-03-09 21:19 (UTC)

Increased verbosity:

  • Does not improve most error messages. The treesitter linker error was not affected by verbosity.
  • Makes finding relevant error messages more difficult.
  • Pushes relevant error messages out of terminal emulator output buffers, especially if the user has not increased them from defaults.
  • Increases log file sizes, potentially making them not fit within pastebin limits.

Increased verbosity does help with problems caused by changes to variables like CC, CXX, CFLAGS, CXXFLAGS, etc. However, this PKGBUILD does not alter any of those variables, so increased verbosity shouldn't be needed.

wsduvall commented on 2024-03-09 12:35 (UTC)

@Farzat do we really need to spew out the entire cc command to the terminal? E.g. cd /home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/build/src/nvim && /usr/bin/cc -DHAVE_UNIBILIUM -DINCLUDE_GENERATED_DECLARATIONS -DUNIT_TESTING -D_GNU_SOURCE -Dnvim_bin_EXPORTS -I/home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/build/src/nvim/auto -I/home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/build/include -I/home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/build/cmake.config -I/home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/src -isystem /usr/include/luajit-2.1 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/home/wsduvall/.cache/paru/clone/neovim-git/src=/usr/src/debug/neovim-git -flto=auto -O2 -g -Og -g -flto=auto -fno-fat-lto-objects -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fsigned-char -fstack-protector-strong -Wno-conversion -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=auto -Wno-conversion -Wno-missing-noreturn -Wno-missing-format-attribute -Wno-double-promotion -Wno-strict-prototypes -Wno-misleading-indentation -Wno-sign-compare -Wno-implicit-fallthrough -Wno-missing-prototypes -Wno-missing-field-initializers -MD -MT src/nvim/CMakeFiles/nvim_bin.dir/__/xdiff/xemit.c.o -MF CMakeFiles/nvim_bin.dir/__/xdiff/xemit.c.o.d -o CMakeFiles/nvim_bin.dir/__/xdiff/xemit.c.o -c /home/wsduvall/.cache/paru/clone/neovim-git/src/neovim/src/xdiff/xemit.c

Farzat commented on 2024-03-08 14:58 (UTC)

@jorges I have no idea why the colorscheme is different. I tried to match the building method to the official package as much as possible, just changing the source to git. Therefore differences are more likely to originate from the source code.

@xiota I know the issue is already fixed (thanks btw), but 0.21.0 is not available yet. If it becomes available I might change back to it.

@wsduvall is there a reason why you want to remove --verbose?

wsduvall commented on 2024-03-06 22:27 (UTC)

Could we remove --verbose from the cmake command?

xiota commented on 2024-02-27 12:40 (UTC) (edited on 2024-02-29 06:38 (UTC) by xiota)

Perhaps the dep on tree-sitter-git can be changed to versioned deps?

tree-sitter>=0.21.0

xiota commented on 2024-02-27 03:28 (UTC) (edited on 2024-02-29 06:40 (UTC) by xiota)

source=("git+https://github.com/tree-sitter/tree-sitter.git#commit=52d69790f36b96ecc1541f6106782ab12786f7cb")

just1602 commented on 2024-02-26 17:39 (UTC)

The package failed to build with this error:

/usr/bin/ld: /tmp/ccvRm0bn.ltrans28.ltrans.o: in function `tslua_init':
/home/goldman/.cache/paru/clone/neovim-git/src/neovim/src/nvim/lua/treesitter.c:171:(.text+0x36aa): undefined reference to `ts_set_allocator'
collect2: error: ld returned 1 exit status
make[2]: *** [src/nvim/CMakeFiles/nvim_bin.dir/build.make:5150: bin/nvim] Error 1
make[2]: Leaving directory '/home/goldman/.cache/paru/clone/neovim-git/src/neovim/build'
make[1]: *** [CMakeFiles/Makefile2:624: src/nvim/CMakeFiles/nvim_bin.dir/all] Error 2
make[1]: Leaving directory '/home/goldman/.cache/paru/clone/neovim-git/src/neovim/build'
make: *** [Makefile:156: all] Error 2

jorges commented on 2024-02-12 17:15 (UTC)

Hi, do you know why this package doesn't use neovim's default colorscheme when used without configuration? Also, typing :help (also without an init.lua) I get errors regarding tree-sitter. I know it is uncommon to run neovim without an init.lua, but first time users can. It happened to me as I was troubleshooting issues with my config. The package from extra is not affected by this problem.