Why is this map added using not showing up?

2018-04-30 22:12:55

From my .vimrc:

nmap s (easymotion-overwin-f)

This sets up an nmap which invokes the EasyMotion plugin when I type ,s.

And that nmap works just fine, and is indeed triggered by ,s.

However, if I do :nmap ,s or :nmap s nvim prints "No mapping found."

Why?

EDIT

Some output from :filter /easy/ nmap:

However, if I do :nmap ,s or :nmap s nvim prints "No mapping found."

Why?

:map (and variants) will return the mappings that Vim/NeoVim is currently using. In your setup you have:

nmap ,, (easymotion-prefix)

There are a few more that easymotion looks to map. Specifically ones that look like:

(easymotion-prefix)N (easymotion-N)

(easymotion-prefix)n (easymotion-n)

(easymotion-prefix)j (easymotion-j)

" So on and so forth

None of the mappings you have a * ahead of the Right-hand-side. See :h map-listing. This means the mappings will trigger other mappings (aka recursive mappings). This mean you can

  • However, if I do :nmap ,s or :nmap s nvim prints "No mapping found."

    Why?

    :map (and variants) will return the mappings that Vim/NeoVim is currently using. In your setup you have:

    nmap ,, (easymotion-prefix)

    There are a few more that easymotion looks to map. Specifically ones that look like:

    (easymotion-prefix)N (easymotion-N)

    (easymotion-prefix)n (easymotion-n)

    (easymotion-prefix)j (easymotion-j)

    " So on and so forth

    None of the mappings you have a * ahead of the Right-hand-side. See :h map-listing. This means the mappings will trigger other mappings (aka recursive mappings). This mean you can trigger (easymotion-N) via (easymotion-prefix)N which is also equivalent to ,,N. There is no ,,N mapping, but due to the maps being recursive and chording (easymotion-N) can still be executed.

    So when you execute, ,,s the ,, maps to (easymotion-prefix) then waits for another possible letter to find another mappin

    2018-05-01 00:40:52