Disabling which-key let doomnvim configuration to fail

[mcctuxic]

Hi,

in doom_config.lua there is written:

    keybinds_modules = {
      -- Core doom keybindings
      core = true,
      -- Movement keybindings, jump between your windows, buffers and code
      movement = true,
      -- Leader keybindings, a bunch of useful keybindings managed by space key
      -- WARNING: disabling this will break which-key plugin if the plugin is enabled
      leader = true,
      -- Completion and snippets keybindings
      completion = true,
    },

The warning let one disable which-key in doom_modules.lua. When nvim is started, which-key will be removed. Next start this message appears: "Check you config for correctness!" which is the second half of a two line message and which first part is not displayed and contains supposedly the information, what has gone wrong. Enabling which-key again fixes that problem...but it
is in contradiction to what the Warning implies.

[NTBBloodbath]

Hey, can you please delete the which-key plugin again and send the output of :mess when the error is raised?

I think it's probably that packer isn't running :PackerCompile as it should so the plugin/packer_compiled.lua could still have the which-key plugin entry 🤔

[mcctuxic]

Hey,
Here are the results: I removed which-key from the config and started nvim. I got a message about removing which-key (1st.png), to which I agreed. Nothing more was displayed then. I run PackerSync then and ended nvim. After restarting nvim I got the message "Check your configuration for correctness"-message and gave the command ":mess" which displayed the message as given in 2nd.png. Then I did a PackerCompile, ended nvim and restarted nvim and got the "Check your configuration...."-message again. 3rd.png shows the message I got after submitting ":mess" again.
Then I reenabled which-key and got message 4th.jpg...which seems somehow unlogical to me...

[osamuaoki]

Did you type Y to the questions?

[mcctuxic]

Yes, I did. Yes, I run PackerCompile afterwards. Yes, I restarted nvim after running PackerCompile. Then I got an error message. After syncing with the repo this morning the error message says: Error in packer_compiled: ...vim/site/pack/packer/opt/packer.nvim/lua/packer/load.lua:13: Err or: attempted to load which-key.nvim which is not present in plugins table! Why is a plugin tried to be loaded after removing it? or Why is it possible to remove a plugin, which makes doom-nvim to fail, if not there?

…

On 09/25 09:30, Osamu Aoki wrote: Did you type Y to the questions? -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #124 (comment)

[NTBBloodbath]

Hi, I think I caught what the error is. I was wrongly assuming that which-key is present and trying to load it in our init file. I'll fix it asap.

Regards

[NTBBloodbath]

Please update Doom and let me know if this still happens

[mcctuxic]

Fixed! Thank you!

…

On 09/26 01:38, Alejandro wrote: Please update Doom and let me know if this still happens -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #124 (comment)