Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Init problem: Attempt to call field 'add' (a nil value) #1079

Closed
DJKero opened this issue Aug 7, 2024 · 6 comments
Closed

Init problem: Attempt to call field 'add' (a nil value) #1079

DJKero opened this issue Aug 7, 2024 · 6 comments

Comments

@DJKero
Copy link

DJKero commented Aug 7, 2024

Describe the bug

kickstart_nvim

To Reproduce

  1. Have the master branch set to the commit of this PR: which-key v3 update #1022. (or newer)
  2. Open nvim.

Desktop

  • OS: Bazzite Stable (Kinoite base)
  • Terminal: Ptyxis 46.5

Neovim Version

NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1720049189

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/home/linuxbrew/.linuxbrew/Cellar/neovim/0.10.1/share/nvim"

Run :checkhealth for more info
@DJKero
Copy link
Author

DJKero commented Aug 7, 2024

I've checked and this happens inside a Distrobox container too.
Going back one commit, to #925, makes the error go away. Don't know if it resolves the underlying issue or if it just avoids the error.

@asthetik
Copy link

asthetik commented Aug 9, 2024

I've checked and this happens inside a Distrobox container too. Going back one commit, to #925, makes the error go away. Don't know if it resolves the underlying issue or if it just avoids the error.

Hello, I also found the same problem, and then I pulled the master branch again, but the problem was still not solved
image

@DJKero
Copy link
Author

DJKero commented Aug 9, 2024

I somehow managed to find a workaround while messing around with both the Brew and the Distrobox packages, poking around by deleting and cloning the repo and using the :Lazy command.

I'm sorry I don't have any clue as to what actually fixed it, but you can try doing the same.

@asthetik
Copy link

asthetik commented Aug 9, 2024

I somehow managed to find a workaround while messing around with both the Brew and the Distrobox packages, poking around by deleting and cloning the repo and using the :Lazy command.

Sorry I don't have any clue as to what actually fixed it, but you can try doing the same.

thank you! fixed this issue your way

@ModEraNoah
Copy link

I had the same issue and calling :Lazy fixed it as well.
The reason for it is that you have to update your dependency packages, which Lazy does. The commit #f5c919558 introduced v3 of the which-key package. Therefore, your local dependency package of the which-key must also be updated.
If just calling
:Lazy does not help, try afterwards to call Update inside of the Lazy UI

@DJKero From my point of view the ticket can be closed as it is not a problem related to the kickstart project but an user-update-issue

@feoh
Copy link
Collaborator

feoh commented Aug 30, 2024

Seems like we're good here now. Please reopen if I'm incorrect.

@feoh feoh closed this as completed Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants