When setting up kickstart.nvim into my fresh neovim installation, the LuaSnip build fails with an assertion error.
--
The specific step appears to be: build: cc -shared jsregexp.o cutils.o libregexp.o libunicode.o -o jsregexp.so
--
The specific stack trace is:
Error detected while processing /home/ccjmne/.config/nvim/init.lua:
E5113: Error while calling lua chunk: ...local/share/nvim/lazy/lazy.nvim/lua/lazy/manage/lock.lua:33: assertion failed!
stack traceback:
[C]: in function 'assert'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/manage/lock.lua:33: in function 'update'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/manage/init.lua:101: in function 'cb'
...cal/share/nvim/lazy/lazy.nvim/lua/lazy/manage/runner.lua:187: in function 'install'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:84: in function 'install_missing'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:44: in function 'setup'
...cjmne/.local/share/nvim/lazy/lazy.nvim/lua/lazy/init.lua:102: in function 'setup'
/home/ccjmne/.config/nvim/init.lua:227: in main chunk
--
Pressing q at that point lets me use neovim normally, and quitting-reopening nvim does seem to have set up at least some things properly (for instance, <space>sh does do exactly what I expected it to).
I'm not sure what is broken in practice in my installation afterwards, assuming anything is broken at all.
NB: I've not used neovim before, and only took a short lua crash course yesterday night, so I might be missing something quite obvious.
To the best of my knowledge, my neovimwas indeed built with LuaJIT: luajit is a dependency of the package I use for neovim (https://archlinux.org/packages/extra/x86_64/neovim/), and running :lua print(jit.version) inside neovim does yield LuaJIT 2.1.1716656478.
The Issue
When setting up
kickstart.nvim
into my freshneovim
installation, theLuaSnip
build fails with an assertion error.-- The specific step appears to be:
build: cc -shared jsregexp.o cutils.o libregexp.o libunicode.o -o jsregexp.so
-- The specific stack trace is:
-- This is the piece of code that ultimately triggers the failing assertion: https://github.com/folke/lazy.nvim/blob/master/lua/lazy/manage/lock.lua#L33
-- Pressing
q
at that point lets me useneovim
normally, and quitting-reopeningnvim
does seem to have set up at least some things properly (for instance,<space>sh
does do exactly what I expected it to).I'm not sure what is broken in practice in my installation afterwards, assuming anything is broken at all.
NB: I've not used
neovim
before, and only took a shortlua
crash course yesterday night, so I might be missing something quite obvious.To Reproduce
rm -rf ~/.local/share/nvim ~/.config/nvim
git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim
nvim
Desktop
6.9.7-arch1-1
zsh
Tools & Versions
I've listed here the version I used of all the tools listed as requirements for
lazy.nvim
andkickstart.nvim
.To the best of my knowledge, my
neovim
was indeed built with LuaJIT:luajit
is a dependency of the package I use forneovim
(https://archlinux.org/packages/extra/x86_64/neovim/), and running:lua print(jit.version)
insideneovim
does yieldLuaJIT 2.1.1716656478
.