-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
%
does not jump between def
and end
, etc (matchit...)
#1885
Comments
the latest version is here https://github.com/vim/vim/blob/master/runtime/pack/dist/opt/matchit/plugin/matchit.vim |
Does anyone have a concise workaround to implement this functionality while we wait? current I'm using |
As requested in #5805, supporting C/C++'s |
I hope this comes eventually! |
There is https://marketplace.visualstudio.com/items?itemName=redguardtoo.matchit for jumping between parens. It doesn't seem to work well for I've tried adding a normal mode key binding for it, but that doesn't seem to work:
|
%
does not jump between def
and end
, etc (matchit...)
Revisiting this as seems like #1840 was closed Anyone found a way to make this work? |
I would love to see this as well. I'm using the |
https://github.com/redguardtoo/vscode-matchit 2.0.0 is released. It add a new algorithm. So it's easier to support customized tags in any programming language. See https://github.com/redguardtoo/vscode-matchit/blob/master/src/cpp.ts for the sample. Pull requests are welcomed. See https://github.com/redguardtoo/evil-matchit for regex samples. |
What would be really neat to have is the two possible matches for xml/html :
Somewhat subtle, but I think it's valuable. |
The VSCodeVim team prioritizes issues based on reaction count.
The
%
key works as expected for single-character block identifiers such as(
/)
, but NOT for multi-char ones such asdef
/end
- such behavior is a staple for being productive in languages like Ruby.I believe the matchit script/macro provides such functionality for actual Vim - more specifically https://github.com/vim-scripts/ruby-matchit.
There's actually the same reported issue over at vscode-ruby but I'm also creating it here as this might be the more appropriate place to solve the problem...
The text was updated successfully, but these errors were encountered: