Parentheses balancing breaks in files with very large forms

[Reiddragon]

Paredit's parentheses balancing breaks in files with very large forms that have a lot of subforms

the bellow file (Tarme's main file wrapped in a module) may be used to reproduce the issue: parentheses balancing is completely broken within the module form

https://gist.github.com/Reiddragon/3b3867470aafb357c3576df30b6b411b

[kovisoft]

Please set g:paredit_matchlines to a higher value in your .vimrc file, e.g. 200 or 300. The default value is 100, which means that paredit looks for matching parens withing this range of lines. As I see, module tarme is 128 lines long, so I assume this is the reason why balancing is broken. Please note that setting g:paredit_matchlines to a very high value may introduce performance issues on slower machines.

[Reiddragon]

welp, that fixed it

btw, might be worth adding some info to the help file about the potential issues with a value that's too high or too low, from the current text I'd struggle to figure out what the variable actually does

[kovisoft]

Do you have a suggestion for an enhanced help text?
And I'm also thinking about increasing the default value, because recently I received an increased number of such complaints, and in all cases it was caused by forms being over 100 lines long. Maybe it would be better set it to 200. What do you think?

[Reiddragon]

Would have to do some benchmarks with higher values on some weaker hardware before settling on something specific, but I think 200 is a safe value performance-wise for most people's hardware

as for a new text, how about something like "Please note that setting this value too high may cause performance issues, while setting it too low may cause parentheses matching to break in large files" (prob not the best wording but I'd say this is a starting point)

Also on the topic of g:paredit_matchlines, does paredit currently support setting this variable only for a buffer? This could help balance the performance issues for people who usually have no issues with a lower value like 100 but occasionally need it set to something much higher like 300

[kovisoft]

Thanks, I'm going to update the documentation accordingly, and also increase the default value to 200.

Currently there is no such option in paredit that you could define per buffer, this is also true for g:paredit_matchlines and TBH I don't think it is really something that one should be able to override for a specific buffer. If needed, it is always possible to set the variable during an editing session via e.g. let g:paredit_matchlines=300, but of course the setting will affect all buffers.

[kovisoft]

Done in commit 60203e5