Andy Massimino

This is an interesting one. vim-jsx-pretty uses a [b:match_words](https://github.com/MaxMEllon/vim-jsx-pretty/blob/c665d5ca4247b696f478f91b7c97b9e44442e4b6/after/ftplugin/javascript.vim#L20) which is subtly broken.. vim-jsx-pretty: `]*\%(/\@\|$\):

Hi. I think you just need to increase the number of lines match-up looks ahead when typing `%`, e.g., let g:matchup_delim_stopline=2000 in your vimrc.

Does the `fn` part matter at all? Are you suggesting that `%` should move between the two backticks?

No, it's not currently supported. Unfortunately, it's difficult to accomplish, since there's no way to tell what is the start and what is the end. I think it would either...

Is it safe to assume you'll want to ignore symbols like `{[(` but jump to *all* active words like `if`, `function`, etc..?

Interesting idea. Can you suggest a convenient mapping? Otherwise this can be an opt-in `` map.

You can try this. It's not perfect, but may work. ```vim let g:matchup_matchpref = {'cpp': {'template': 1}} ``` Doing it properly is going to require vim to understand syntax much...

What is the file type you are using? Do you use any jinja2 plugin?

Should be possible to define a set of regexes for the jinja tags, like ```vim au FileType jinja let b:match_words = get(b:, 'match_words', '') \ . ',{%-\?\s*if.\{-}-\?%}:{%-\?\s*else\s*-\?%}:{%-\?*\s*endif\s*-\?%}' \ . ',{%-\?\s*for.\{-}-\?%}:{%-\?\s*endfor\s*-\?%}'...

Is there any way you can test this with vim instead of neovim? I wonder if this is a difference in the way CursorMoved is handled between vim/neovim, a bug...