-
Notifications
You must be signed in to change notification settings - Fork 175
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
Virtual env bin/python
buffer remains open after :VimspectorReset
#795
Comments
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. |
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. |
Can you please share your normal configuration at least? |
Can you try #796 ? |
I will later today. Thank you for this super fast response. I will update you. |
An update on this. It seems that the last buffer is handled but if I use |
Also, the same effect is happening when the debugging session is interrupted. Meaning, if I press |
Description
When using Vimspector with Python virtual environment, the buffer created for displaying the Python output remains open after
:VimspectorReset
is called. This results in having multiple buffers open, one for each run of the debugger.Is it reproducible in vim?
Reproducible in Vim
Works with clean config?
Yes
Sample project works?
Reproducible with sample project
Minimal Reproduction
List of steps to reproduce:
pipenv shell
vim ---clean -Nu /path/to/vimspector/support/minimal_vimrc ....
:e test.py
:ls
and see the open buffers<F4>
.:ls
and observe the buffers. You will something like:Expected Behaviour
The buffers should be closed/deleted as happens when Vimspector isn't using Python inside virtual env.
Actual Behaviour
The Python output buffers are not deleted with Vimspector uses Python from a virtual environment.
Additional information
No response
Installation Type
Plugin Manager (git clone)
Vimspector version
4e49a17
Debug Info
Log file
Vim version
Python version
3.11.4 (main, Jun 7 2023, 00:34:59) [Clang 14.0.3 (clang-1403.0.22.14.1)]
Neovim diagnostics
No response
Operating System
MacOS
Declaration
The text was updated successfully, but these errors were encountered: