fix: prevent buffer jump when safe strategy fails #96
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.
When
replace-buffer-contents
fails to do a non-destructive replacement within the allotted time/cost, it basically follows thefast
strategy, except unlike thefast
strategy, it doesn't try to prevent the window from jumping.So in addition to doing the window adjustment in the
fast
strategy, we can also do it for thesafe
strategy when it fails and returnsnil
.