Wipe out scratch buffers #893
Open
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
|
This change is |
Some people are really picky about their buffer numbers and not having unlisted, unloaded buffers in the buffer list. I personally don't care and like the fact that marks and stuff are retained between runs, but I don't care enough to really fight it. This is cleaner afterall. Closes #879
puremourning
force-pushed
the
wipe-out-buffers
branch
from
d40629a to
0cccd4e
Compare
The comment explains, badly, that there is a bug somewhere that when we wipe out the disassembly buffers, we end up with: || Caught exception in Test_Disassembly_Open_Close(): Vim(py3):vim.error: Vim(py3):vim.error: attempt to refer to deleted buffer But I can't work out why exactly. Wiping out the buffer causes this, but deleting the buffer doesn't.
puremourning
force-pushed
the
wipe-out-buffers
branch
from
0cccd4e to
a3bbebc
Compare
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.
Some people are really picky about their buffer numbers and not having unlisted, unloaded buffers in the buffer list. I personally don't care and like the fact that marks and stuff are retained between runs, but I don't care enough to really fight it. This is cleaner afterall.
Closes #879