Make idris-response buffer better behaved in terms of buflist and jumplist #22
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.
I also did a refactor and put all functions into autoload for namespacing and lazy loading purposes.
The only behavioral changes are in
idris2#responseWinandidris2#write(formerly IdrisResponseWin and IWrite). Now the idris-response buffer is a proper scratch buffer (see:help special-buffers), and writing to it tries not to change any window buffers if possible. Both of those things also improved performance because vim doesn't have to rerender the code window if scratch buffer is visible.