Andy Massimino

Does the output of at synID stabilize if you call it more than once in the same position?

Yes, I definitely saw a similar issue when developing vim-matchup and I worked around it exactly as you say. However, I never correlated the issue to conceal in particular so...

The Go language is supported only in neovim + Treesitter, it cannot be supported using regex. Hugo works as described. Also described in wiki https://github.com/andymass/vim-matchup/wiki/The-match-up-wiki

There are some security issues which should be addressed before considering distribution with vim. Modelines are widely considered insecure, but editorconfig is much worse. Consider: ```ini charset = cp932 |...

Here is another exploit. Allows sourcing any vim script regardless of user's settings. [*] charset = cp932 foldexpr:execute(\"let\ g:editorconfig_local_vimrc\\75\ 1\") foldmethod:expr foldenable foldlevel:0 local_vimrc = exploit Just to be clear:...

If possible I would recommend avoiding vim-repeat. Instead you can use vim's native `g@` like in this example: https://gist.github.com/andymass/d465970cc178452eac006840e5e58b2b Specifically, although `g@` is usually used as the start of normal...

> Can't you use the g@l hack already now in your config? Yes, it's possible via a wrapper function; ```vim function! s:repeatable(cmd) function! s:inner(...) closure abort execute a:cmd endfunction let...

Vue is supported without any extra plugin now in modern versions of vim. If you're using an old version of vim, you can create a file `.vim/after/ftplugin/vue.vim` or `.vim/ftplugin/vue.vim` containing:...

Closing as it's supported with tree-sitter. Unfortunately, we can't support this in vanilla vim today.

@adriantrunzo Thanks, I was never really satisfied with this motion's implementation, I kept running into ergonomic issues when testing, and never got a chance to revisit it. Would you mind...