Virtual env `bin/python` buffer remains open after `:VimspectorReset` about vimspector HOT 8 OPEN

Can you try #796 ?

from vimspector.

Thanks for the report. Weird one. Doesn't reproduce in my normal configuration, but I can repro with the minimal vimrc.

It seems pretty low priority to me though, as I can't immediately see what actual problem this causes.

from vimspector.

The problem is that when debugging, Vim gets filled with buffers. Manually closing them kinda diminishes much of the experience.

The weird thing is that once I have opened Vim and did debugging but it worked as it should. I don’t know what made it work normally, but this was once. Now it is back to not working as it should.

from vimspector.

Can you please share your normal configuration at least?

from vimspector.

I will later today. Thank you for this super fast response. I will update you.

from vimspector.

Yes, it works. Now I'm getting this:

You can see that the number of the buffers is different, but the previous buffers are not open now. They are closed.

Thank you once more. Please give an update when you do the merge.

from vimspector.

An update on this. It seems that the last buffer is handled but if I use gt to switch tabs, the fix breaks and not working for the open buffers. That is, if I end a debugger run and there is an open buffer, e.g. buffer 1, and then I do gt to switch tab and again gt to go back to Vimspector, then the next time I will run the Vimspector, buffer 1 will not be cleared and buffer 2 will be created.

from vimspector.

Also, the same effect is happening when the debugging session is interrupted. Meaning, if I press <F4>/<F3> before the debugging session is ended normally, then the buffer remains open.

from vimspector.