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
I am not sure if it's a bug however my Vomnibar.activateTabSelection is set to "c-space"
If I am writing text in whatever box the feature no longer works (In claude prompt box for example. Or youtube search bar). If I press the keybinding the default brave shortcut happens.
Now I assume vimium is just "deactivated/disabled" when in "insert mode" and only waits for escape. Can this be overwritten?
Basically what I want is to be able to use the TabSelection even when in insert mode. If anyone knows a way around this or can help me out greatly appreciated!
Using Chrome based browser (Brave)
The text was updated successfully, but these errors were encountered:
From how I understand it, "insert mode" in Vimium is meant to disable all Vimium keybindings except for escape, in order to send any key events directly to the underlying page instead of intercepting those events. This allows users to have their Vimium bindings active on sites and still have a way to access keybindings that are implemented by the website itself, e.g. YouTube, Google Docs and many more have a bunch of key bindings that would otherwise be "overridden" by Vimium's (default) keybindings.
From what I know, in Vimium it is currently not possible to define key bindings for "insert mode".
I am not sure if it's a bug however my Vomnibar.activateTabSelection is set to "c-space"
If I am writing text in whatever box the feature no longer works (In claude prompt box for example. Or youtube search bar). If I press the keybinding the default brave shortcut happens.
Now I assume vimium is just "deactivated/disabled" when in "insert mode" and only waits for escape. Can this be overwritten?
Basically what I want is to be able to use the TabSelection even when in insert mode. If anyone knows a way around this or can help me out greatly appreciated!
Using Chrome based browser (Brave)
The text was updated successfully, but these errors were encountered: