You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes Vimium interferes with websites shortcuts...
Great feature would be :
(separate if user wishes) shortcuts to enable/disable (suspend?) Vimum other shortcuts
separate so it's idempotent and I don't have to remember if in given browser/tab/session it's on or off, if I press "turn on" shurtcut I know it turns on, if I press "turn off" shortcut then I know it disables, what helps to develop also muscle memory etc...
ability to select if by default Vimum is in "suspended' mode. some users may use Vimium occasionally so prefer to have it's shortcuts disables by default , others don't etc...
also currently in settings one can select which sites are excluded, however here maybe users that may want to do opposite, select for wihch sites it's turned on. (which should be probably separate separate github issue so if you find it interesting, please don't hesitate to make new issue)
The text was updated successfully, but these errors were encountered:
Was looking for something similar, might be a temporary fix--Try passNextKey. This suspends Vimium for a single keystroke. I found this useful for basic commands like passing / to Google or GitHub to focus the search bar. Not a perfect implementation, but maybe a step in the right direction?
Thanks for the hint. Mapping passNextKey seems like a good way to for example be able to pass f on youtube. Too bad it isn't mapped by default and thus doesn't show up on the default help page. I suggest adding a mapping by default.
As with all other multi key commands that move to a temporary "mode" while waiting for the next key, I find it slightly confusing that this state isn't shown in any way. I think a status message in the corner while waiting for the next key would be a nice improvement.
Sometimes Vimium interferes with websites shortcuts...
Great feature would be :
The text was updated successfully, but these errors were encountered: