-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to ‘map g’ #252
Comments
This is also an issue in vim itself. I think the only way to map just |
Is there some quick way to grep all the bindings that start with g? Or do I
have to go through :help looking for them, hoping I won't miss any?
|
|
No cigar:
still doesn’t work. |
Thanks for trying. It's possible that it's mapping specially. In which case a change to the code would be necessary beforehand. |
As a reference of sorts: If a map is not executed, chances are that longer maps starting with the same key sequence still exist. Take a look at events.js' onKeyPress logic. Using explicit internal functions:
If a simple Same goes for mappings with keys that are not used anywhere else, such as
Now I don't think adding lots of maps to If you really want to use tl;dr bad idea. Closing, as this issue doesn't have a "solution" with the current design. |
If someone can go through and figure out how to make vimperator actually acknowledge a full set of |
I’m trying to use ‘g’ to switch to the next tab. In desperation, this is what I used:
Unfortunately, ‘g’ is still recognized as a prefix only so on its own it does nothing, but ‘gg’ scrolls to the top. The same issue is with ‘z’ which is also a prefix key.
The text was updated successfully, but these errors were encountered: