mini.files with LazyVim: difficult to come up with keymap for set_cwd

[proofer]

With mini.files open, 'g?' says use 'gc' to set cwd. But 'gc' brings this up:

I.e, 'gc' conflicts with Toggle comment. Likewise, 'g~' , which is used in doc/mini-files.txt in an example autocmd at line 530, conflicts with 'Toggle case'. I used the autocmd example code to set the keymap to 'g}'. That works to change the cwd, but it confuses which-key, which now shows both the original 'gc' and my 'g}' on consecutive 'Set cwd' lines in response to 'g'.

[echasnovski]

Sorry, this is more question to LazyVim than 'mini.files'. Example in 'mini.files' for g~ mapping works with standalone 'mini.files' and with 'mini.clue' (as it is not enabled in 'mini.files' by default). The g? menu shows all buffer-local mappings, so the local gc might be added somewhere else (as it is not a part of 'mini.files').

My suggestion would be to ask in LazyVim or 'folke/which-key.nvim' discussions.

[proofer]

Fair enough. I assumed you and Folke and several other members of the nvim pantheon ate lunch together every day, but perhaps not...

[echasnovski]

Fair enough. I assumed you and Folke and several other members of the nvim pantheon ate lunch together every day, but perhaps not...

Not lunch every day, but more or less being aware of the work in the Neovim plugin world indeed. But for me keeping up with LazyVim customization proved to be a bit much, sorry.