Fix using an invalid scratch buffer #86
Closed
Conversation
This file contains 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
tot0rokr
force-pushed
the
invalid-scratch-buffer
branch
from
2e4652f to
35187b8
Compare
|
thanks, I've translated your patch into a compatible version: |
|
@skywind3000 This is sad, because open source is supposed to be fun to contribute to. |
|
Sorry, next time I will disscuss with you at the first place about my thoughts before taking any action. Anyway, no need to be sad, it is your idea, I will mention this in the new release information. |
|
Okay. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was an issue where opening, closing, and reopening Terminal in Neovim would access a buffer that had already been “wiped”.