FS#76107 - [neovim] 0.8.0-3 misses bundled treesitter parsers
Attached to Project:
Community Packages
Opened by Yufei Wu (yufei) - Tuesday, 04 October 2022, 04:18 GMT
Last edited by Daniel M. Capella (polyzen) - Sunday, 16 July 2023, 05:56 GMT
Opened by Yufei Wu (yufei) - Tuesday, 04 October 2022, 04:18 GMT
Last edited by Daniel M. Capella (polyzen) - Sunday, 16 July 2023, 05:56 GMT
|
Details
Description:
Upstream neovim 0.8.0 bundles C, Lua, and Vimscript treesitter parsers. Community package neovim 0.8.0-3 misses them. Additional info: Upstream release note: https://github.com/neovim/neovim/releases/tag/v0.8.0 Steps to reproduce: 1. neovim 0.8.0-3 package $ nvim --clean --cmd checkhealth vim.treesitter: require("vim.treesitter.health").check() ======================================================================== - INFO: Runtime ABI version : 14 2. upstream 0.8.0 appimage $ ./nvim.appimage --clean --cmd checkhealth vim.treesitter: require("vim.treesitter.health").check() ======================================================================== - INFO: Runtime ABI version : 14 - OK: Loaded parser for c: ABI version 13 - OK: Loaded parser for help: ABI version 14 - OK: Loaded parser for lua: ABI version 13 - OK: Loaded parser for vim: ABI version 14 3. extract the appimage $ ./nvim.appimage --appimage-extract Parsers can be found in ./squashfs-root/usr/lib/nvim/parser/ |
This task depends upon
Closed by Daniel M. Capella (polyzen)
Sunday, 16 July 2023, 05:56 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.1-2
Sunday, 16 July 2023, 05:56 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.1-2
Comment by
Caleb Maclennan (alerque) -
Wednesday, 19 October 2022, 11:06 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Sunday, 12 March 2023, 09:15 GMT
I think this should be considered an upstream issue. We're running
`cmake --install build` and packaging everything it outputs. The
above mentioned parsers are not being installed by the upstream
maintained install routines. As such –and since they are not
distro specific– I would say it's up to upstream to decide what
does and does not get installed by default. Unless there is some
option we're missing to enable these...
Is there an upstream issue about this?