Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wipe out scratch buffers #893

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Wipe out scratch buffers #893

wants to merge 4 commits into from

Conversation

puremourning
Copy link
Owner

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

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
Copy link
Owner Author

This change is Reviewable

Previously we were starting and resetting immediately, but sometimes if
this was slow we could end up in the exception breakpoints prompt and
stuck until timeout. Supress the prompt.
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Many unlisted buffers are left opened after :VimspectorReset
1 participant