Something that puzzled me for quite awhile was why the comma menu wouldn't appear and what to do to get it back. The solution seems to be to invoke <space> l l to reinitialize something inside LSP. Is this expected behavior? If so, I suggest a note somewhere in the documentation.
There is a new major release of which-key (a significant rewrite) that should fix the , menu issue.
https://github.com/folke/which-key.nvim/pull/624
I will try this out over the weekend
I have noticed this myself and do not have a definitive answer as yet.
I suspect its due to some aspect of lazyness in loading the whichkey package or the package that has the which-key definitions (although I dont have any direct evidence)
In some very brief testing, SPC followed by Esc seems to be enough to kickstart the , local leader menu. I assume any SPC key binding would ensure which-key is loaded.
Astronvim has the which-key marked as VeryLazy. I'll see if I can get some info from the AstroNvim discord community.
Seems the menu not showing is a reported bug with Which-key. Unfortunately its a bug that has been around for over a year, so not sure when it will be fixed. https://github.com/folke/which-key.nvim/issues/476
There are some suggestions on how to fix for certain plugins, so I will try and see if I can create something for conjure. I also noticed the conjure menus are not showing the text descriptions (for parent menus). So something else to investigate.
> I also noticed the conjure menus are not showing the text descriptions (for parent menus). Yes!
The SPC Esc trick worked for me on a lua buffer, but the localLeader doesn't work on a python file.
I'll Add conjure sub-menu names in the next few days. i don't know a fix for which-key, I assume we have to libe with it I hvent done python dev in a long time, but happy to add something to the config if it helps.