-
Notifications
You must be signed in to change notification settings - Fork 25
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
Plug mappings are ambiguous #9
Comments
chrisbra
added a commit
that referenced
this issue
Jun 30, 2012
Thanks for the detailed feedback. I fixed it and it should work now. |
Who is Peng Su? :)
|
Sorry, I'll update it in the documentation. |
Oh please, don't bother. That's very polite of you, but very unnecessary! Cheers |
chrisbra
pushed a commit
that referenced
this issue
Jan 23, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
The plug mappings
<Plug>NrrwrgnDo
and<Plug>NrrwrgnDo1
are ambiguousand cause a slight delay of
timeoutlen
ms, or a complete pause ifset notimeout
.What is happening is that Vim sees that the first mapping may
potentially be a subset of the second mappings and waits for
timeout
ms before executing the mapping. If
notimeout
is set, it waits foruser input to disambiguate the name clash. At this point the user can
actually trigger
<Plug>NrrwrgnDo1
by pressing:<Leader>nr1
!I changed my local copy to simply rename the bang versions of the plugs
to
<Plug>NrrwrgnBangDo
and<Plug>VisualNrrwBangRgn
to resolve.BTW, this is a separate issue, but the new mapping
<Leader>Nr
does notreuse the same window like
:NR!
, as it seems intended to do.Thanks for the software!
The text was updated successfully, but these errors were encountered: