Feature: Option to set motion timeouts about vim-matchup

[MCredstoner2004]

Ah sorry, I just can't type, it was 3881 and 3882, I'll update the previous comment just so the reproduction steps should be all there, as for config, I only configured the aforementioned stopline variables, and enabled the treesitter backend.

[andymass]

Can you share the C++ file in question, or at least one having the issue?

I agree optimizing find_unmatched using more TS features is needed at this point. Adjusting timeouts is fine but it's better if we can return the result quickly.

[andymass]

Another thing that we can try is if this suggestion changes the performance: #302 (comment)

If so, then it may be isolated to that specific functionality.

[MCredstoner2004]

Can you share the C++ file in question, or at least one having the issue?

Yeah, I wasn't working with a file this big when I made the feature request, but since I've tested this issue on my desktop instead of my laptop, and to be able to reproduce it I had to create a much larger file
main.cpp.zip
(the file was generated by replacing a deduced type with a fully deduced one in an expression tree like matrix library I'm working of as a side project, it wouldn't be expected for anyone to write a type that specific, but that's the easiest quickest way I found of generating valid C++ code.)
If you set the cursor at line 3881 find_unmatched should go well over timeout on almost any device and as a result you can't do [%, however, if I out the cursor on the next line (3882) I immediately get the popup showing the matching namespace opening, and can jump to it just fine with %.
Due to the number of lines in the file, I increased the stopline variables to over 9000, and even on my laptop, I still get the popup with the matching bracket almost instantly.

[andymass]

Interestingly I can't seem to reproduce this.

From line 3381 [% goes to line 3147 due to the < in under 200ms

From line 3382 [% goes to line 3381 again on the < in under 50ms.

Could I be missing anything config-wise?