-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Non leader keys #113
Comments
No only the leader and localleader, but also any key mappings defined explicitly. vim-which-key retrieves the info of key mappings via It's possible to also support the builtin default mappings, but someone needs to spend time on it. Related #14. |
I found what I want exactly. nnoremap <silent> g :<C-U>WhichKey 'g'<CR>
let g:which_key_fallback_to_native_key = 1 The vim default key mappings are still not shown, but they are accepted instead of banned as "[which-key] ... is undefined". |
@nkcfan With these settings goes operators such as |
Cool catch! I tested |
Did you mean |
|
Didn't know about the guu gUU commands actually, so learnt something new 🙂 But indeed not working |
Btw, just noticed that with the above settings also commands such as |
The fallback call only works for 2 key mappings since it is calling the entered keys immediately. @liuchengxu happy to submit a PR if this looks good to you |
@acdifran That looks good to me, feel free to send a PR. |
Is your feature request related to a problem? Please describe.
Seems vim-which-key is designed to work with key mappings following leader or localleader. I experiment it with other leading char, such as
g
which is commonly used. I notice some issues.[which-key] g J is undefined
Describe the solution you'd like
I am ok if it is difficult to show the vim default key mappings, but I really wish they still work.
Describe alternatives you've considered
Not to use vim-which-key with non leader characters.
Additional context
N/A
The text was updated successfully, but these errors were encountered: