Like I said, I haven’t used mini.comment, but having both gc
and gcc
mapping may cause problems. If I remember correctly, in these situations, neovim waits after receiving gc
command to figure out if you are trying to execute comment last
or gcc
with comment line
. Depending on timelen
(or timeout, forgot the exact name) setting the command you actually execute will defer based on the key pressed/not pressed after gc
.
Also, if gc
is mapped to comment last
, and there was no last comment action performed, it might do nothing (maybe check the readme to be sure). So maybe try changing the mapping to see if that helps.
That makes sense. Which-key doesn’t allow the timeout to take place after gc since it knows about gcc. While that functionality is useful when you don’t know which key to press next, in situations like these it would create problems. I think your best solution would still be to modify the mappings. Maybe remap gc to gcl (comment last) or something like that.