Andy Massimino

The behavior in matchit is the same. I think it is due to a problem with `b:match_words` set by the `ftplugin/sql.vim` (maintained by David Fishburn). This example still seems challenging....

This may work for you. Place it in your vimrc or wherever it can be run before opening files of type `sql`. ```vim " test/issues/3/hotfix.vim function! SQLHotFix() call matchup#util#patch_match_words( \...

Glad it's _mostly_ working for you :smiley:. You are right, I should have thought of that example. Anyway, I cannot think of a way to handle this correctly with the...

Do you have any thoughts about the patch proposed in vim/vim#4010? Would it cover your plugin's needs? Note that it's not really necessary to add an "asynchronous" API to the...

Admittedly I am not following all the linked conversations, but is the "diff" issue you mentioned just that you can't keep track of diagnostics when the text is being edited?...

Sorry, text properties is a feature of vim not lsp. Basically like marks except they track columns and can use highlighting. I'm thinking you'd add the received diagnostics as text...

Compare: :let &statusline='%{"L"}%{" |"}' to :let &statusline='%{"1"}%{" |"}'

Apparently it is the same as this feature/bug: https://github.com/vim/vim/issues/1431 When an expression evaluates to an all digits string, it is handled as a number and not a flag (set `itemisflag...

@cutejs, your problem sounds unrelated to this issue, but the workaround for the stated problem is to append a trash character to the number. This works for me: function! AirlineWinnr()...

Thanks for your input! > As a site note I must admit that I don't use this plugin myself atm. Totally understand if this plugin doesn't fit your current workflow...