You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
0.9.2
Operating system/version
EndeavourOS
Describe the bug
When in lazy.nvim's popup window viewing plugins and pressing enter causes an error to occur, preventing me from viewing information about the plugin:
Error log from Neovim:
Error executing vim.schedule lua callback: vim/shared.lua:0: s: expected string, got nil
stack traceback:
[C]: in function 'error'
vim/shared.lua: in function 'validate'
vim/shared.lua: in function 'gsplit'
vim/shared.lua: in function 'split'
.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/view/text.lua:31: in function 'append'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:340: in function 'reason'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:539: in function <...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:537>
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:563: in function 'props'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:546: in function 'details'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:436: in function 'plugin'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:250: in function 'section'
...local/share/nvim/lazy/lazy.nvim/lua/lazy/view/render.lua:71: in function 'update'
.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/view/init.lua:143: in function 'fn'
.../jade/.local/share/nvim/lazy/lazy.nvim/lua/lazy/util.lua:81: in function <.../jade/.local/share/nvim/lazy/lazy.nvim/lua/lazy/util.lua:80>
Press ENTER or type command to continue
After encountering that error, it becomes impossible to view any other plugins or the plugin itself, regardless of how many times the enter key is pushed.
Steps To Reproduce
Open Neovim
Open up lazy.nvim using :Lazy
Move cursor over plugin that uses keys to specify lazy loading
Press enter
Notice how the error occurs
Move cursor over to different plugin
Press enter
Notice how nothing happens
Expected Behavior
An error should not show, and I should be able to view information about the plugin when pressing enter with my cursor on the selection, viewing things like the directory, url, version, tag, etc. along with any other plugins
Repro
-- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
-- add any other plugins here
{
"numToStr/Comment.nvim",
config=true,
keys= {
{ "gc", mode= { "n", "v" } },
{ "gb", mode= { "n", "v" } },
},
},
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
Neovim version (nvim -v)
0.9.2
Operating system/version
EndeavourOS
Describe the bug
When in lazy.nvim's popup window viewing plugins and pressing enter causes an error to occur, preventing me from viewing information about the plugin:
Error log from Neovim:
After encountering that error, it becomes impossible to view any other plugins or the plugin itself, regardless of how many times the enter key is pushed.
Steps To Reproduce
Expected Behavior
An error should not show, and I should be able to view information about the plugin when pressing enter with my cursor on the selection, viewing things like the directory, url, version, tag, etc. along with any other plugins
Repro
The text was updated successfully, but these errors were encountered: