3
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Nov 2023
3 points (100.0% liked)
Neovim
2155 readers
1 users here now
founded 1 year ago
MODERATORS
Try using
:verbose nmap gcto find out what the shortcut is currently mapped to.I don't use mini.comment, but I assume it needs an operator after
gcto for commenting. I have seengccused to comment out the line. Just wanted to make sure you are using the correct mapping.This is what is showed after doing :verbose namp gc, seems that all is ok....still if I press gc // on commentig line a search command is done...if I try on commented line with gcc command the line is cleared...
n g * lua require("which-key").show("g", {mode = "n", auto = true}) Last set from Lua
n gcc * Comment line Last set from Lua line 293
n gc * Comment Last set from Lua line 293
Like I said, I haven't used mini.comment, but having both
gcandgccmapping may cause problems. If I remember correctly, in these situations, neovim waits after receivinggccommand to figure out if you are trying to executecomment lastorgccwithcomment 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
gcis 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.