Not all leader mappings picked up from other plugins (lusty) about vim-which-key HOT 16 CLOSED

vim-which-key takes mappings from :map, what do :map <leader>lb and other :map <leader>l say?

from vim-which-key.

:map l output screenshot below

Hitting SPACE (my leader) invokes which-key, screenshot:

from vim-which-key.

Looks like if more than one chars are in the leader mapping, only one of them shows up. Here's the full output of :map <leader>. Note how I have many <leader>h bindings, but only two show up.

from vim-which-key.

Have you updated vim-which-key to the latest version? If so, please provide a minimal vimrc to help reproduce. It works for me.

from vim-which-key.

from vim-which-key.

Updated to d326c18 on master, still have this issue. Do you have your minimal .vimrc to check against? Can you share?

from vim-which-key.

Also, I don't fully understand +prefix usage. I have nmap <leader>l :set list!<CR>, and if I remove it from my .vimrc, I see l -> +prefix in which-key window, selecting it shows all leader bindings of l.

from vim-which-key.

Quick example:

set nocompatible

call plug#begin()
Plug 'liuchengxu/vim-which-key'
call plug#end()

let g:mapleader="\<Space>"

nnoremap <silent> <leader>      :<c-u>WhichKey '<Space>'<CR>
nnoremap <silent> <localleader> :<c-u>WhichKey  ','<CR>

nnoremap <Leader>1 :echom "THis is one"<cr>

let g:which_key_map = {}

let g:which_key_map.1 = ['echom "This is one"', "One"]

call which_key#register('<Space>', "g:which_key_map")

+prefix is the default group name, see https://github.com/liuchengxu/vim-which-key/blob/master/plugin/which_key.vim#L21, that means you have a number of mappings leading by <Leader>l*. However, if you have a mapping <Leader>l, then vim-which-key will display it rhs instead.

from vim-which-key.

from vim-which-key.

rhs means right-hand-side, see :h rhs.

from vim-which-key.

Thanks. Can you share the .vimrc section related to which-key, which produces the screenshot you sent earlier

from vim-which-key.

Here is my config https://github.com/liuchengxu/space-vim. I also change the highlight of WhichKeyDesc in the pict:

highlight WhichKeyDesc ctermfg=68 guifg=#5f87d7

from vim-which-key.

However, if you have a mapping <Leader>l, then vim-which-key will display it rhs instead.

I have only this l key mapped in my .vimrc:

nmap <leader>l :set list!<CR>

lusty explorer provides these:

nmap <silent> <Leader>lf :LustyFilesystemExplorer<CR>
  nmap <silent> <Leader>lr :LustyFilesystemExplorerFromHere<CR>
  nmap <silent> <Leader>lb :LustyBufferExplorer<CR>
  nmap <silent> <Leader>lg :LustyBufferGrep<CR>

If I understand you, which-key would only show nmap <leader>l :set list!<CR> mapping.
But if you look this screenshot, one of the lusty's l mappings is also shown.

Your .vimrc suggest the use of dictionary for such cases, is it needed for such cases (single letter and same letter in multiple letter combinations, like l and lb)?

from vim-which-key.

By default it will show other <leader>l* instead of <leader>l only, see https://github.com/liuchengxu/vim-which-key/blob/master/plugin/which_key.vim#L13. You could try this if you don't want that:

let g:which_key_flatten = 0

If you have two mappings <Leader>l and <Leader>lb, when you press <Leader>l, I don't know whether you want to trigger <Leader>l or in the middle of <Leader>lb, see :h ttimeoutlen, so I suggest avoid such mappings. Don't map <Leader>l when you have <Leader>l* mappings.

Read https://github.com/liuchengxu/vim-which-key#configuration and the doc please.

from vim-which-key.

from vim-which-key.

Closing then. Feel free to reopen if you still have questions.

from vim-which-key.