fix: cache indent matches to avoid occasional race conditions #640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a really weird bug. I know it's an issue with how the
get_matches
function works and buftick.indentexpr
isn't really intended for indenting many lines that all depend on each other's indents.What this does is "freeze" the matches during a indent operation against a range of lines and only updates the previous matches' indent as necessary. By doing this we get "memory" for the indentexpr of the previous indents as part of a ranged indent operation like
norm! 0gg=G
which avoids any race conditions as to the speed of indents. Without this caching theget_matches
function is called on every indentexpr operation, so for every line in the range, which can result in bad data back for calculating the indents.I have added a big ol' comment above the indentexpr with further information.
Closes #639