Closed lkyhfx closed 1 year ago
Same gitsigns error on my end. Appears sporadically during Nvim startup. Seems like maybe some kind of async issue based on the coroutine message in the stacktrace?
Failed to run `config` for gitsigns.nvim
...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:64: The coroutine failed with this message: ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/signs.lua:23: att
empt to call field 'new' (a nil value)
stack traceback:
^I...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/signs.lua: in function 'new'
^I...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:544: in function 'setup'
^I...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:399: in function <...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:377>
# stacktrace:
- ~/.local/share/nvim/site/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:64 _in_ **step**
- ~/.local/share/nvim/site/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:79 _in_ **setup**
- ~/.config/nvim/init.lua:66
OS: MacOS Ventura 13.3.1 Neovim: v0.9.0
Hi there folks thanks for the report!
This does indeed look like an issue. However, kickstart.nvim is just a collection of configurations and doesn't own all the code for al the plugins we reference :)
Might I suggest that you please go open an issue on their repo.
Thanks again and I hope this gets resolved quickly for you!
Describe the bug A clear and concise description of what the bug is. Open neovim, these errors pop up randomly
To Reproduce Steps to reproduce the behavior:
nvim
Desktop (please complete the following information):
Neovim Version
:version
from inside of neovim: 0.8.3