Improve performance by avoiding unnecessary highlighting updates #171
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The vim-better-whitespace plugin currently resets whitespace highlighting whenever the
CursorMovedIorCursorMovedevents are triggered, in order to exclude the current line from highlighting. However, this results in redundant highlight updates when the cursor moves within the same line.This PR optimizes performance by skipping the highlight reset if the
CursorMovedIorCursorMovedevents are triggered without a change in the current line. This reduces unnecessary processing, enhancing responsiveness during cursor movements.