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.
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.
Try using :verbose nmap gc to find out what the shortcut is currently mapped to.
I don’t use mini.comment, but I assume it needs an operator after gc to for commenting. I have seen gcc used to comment out the line. Just wanted to make sure you are using the correct mapping.
If you are trying to switch from Chrome, then just use regular Firefox with the ublock extension (and maybe some of the other privacy extension officially supported). If you are a “power user” and want modify/access about:config and other settings then you need Firefox Nightly. The Fennec and Fenix (iirc) are just stripped down Firefox that either only have private mode or additional settings for privacy (that are already present in regular version, but way not be enabled by default). Hope that helps.
Next time, try enabling display of whitespace characters through
set list. If I remember correctly, they can help distinguish between the Windows carriage return character and Linux end of line character.This may help for a quick overview.