this post was submitted on 22 Nov 2023
2 points (100.0% liked)
Neovim
2061 readers
1 users here now
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Like I said, I haven't used mini.comment, but having both
gc
andgcc
mapping may cause problems. If I remember correctly, in these situations, neovim waits after receivinggc
command to figure out if you are trying to executecomment last
orgcc
withcomment line
. Depending ontimelen
(or timeout, forgot the exact name) setting the command you actually execute will defer based on the key pressed/not pressed aftergc
.Also, if
gc
is mapped tocomment 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.it seems that which-key create conflict with mini.commnet...if I disable it gc and gcc works according....now I don't know how to let both plugin live togethere
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.