Do not include cursorline in the default configuration since it incurs a significant CPU hit#887
Open
Do not include cursorline in the default configuration since it incurs a significant CPU hit#887
Conversation
…s a significant CPU performance hit
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.
Prior to this commit, I would often observe Vim using 100% CPU while scrolling through a basic PHP or CSS file with the common, "j" and "k" motion commands. After profiling Vim under various configurations, I isolated the cause to "set cursorline" in .vimrc. Upon disabling cursorline, I was able to navigate the same files at ~10% CPU utilization.
":help cursorline" shows the following