-
Notifications
You must be signed in to change notification settings - Fork 171
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
Vim:E158: Invalid buffer name <name> when starting debugging in neovim #131
Comments
Can you please try with a minimal vimrc and the simple example in
I can't repro with that. You might need to use a custom minimal
|
Have attempted the single command and it gives the following prompt one I run it
Attaching gives the following result.
Clicking option 2, run, gives the following
and clicking option 3 gives,
The first and third option to not kick off the debugger, i.e. split the tab into its windows. Next I tried to run a custom minimal vimrc which consisted of the following.
I ensured the the python providers were all setup correctly tthrough :checkhealth and this had an indentical result to the result mentioned previously. |
This is expected, it's because the legacy adapter isn't installed. I just pushed a quick change to make this a proper error message (as it happens regularly enough).
I was able to repro this just now. I can't repro in Vim. I'll look into it, but neovim is a constant pain in my gut, and it's not a priority for me. |
I suspect this regression happened due to c4bedce, though I dont know why that would cause it. |
vim worked flawlessly for me when I tried it, spend a decent amount of time looking up the error but couldnt come to any reasonable conclusion. I will attempt to set it up tomorrow on a linux machine and see if it gives the same error |
Yep similar problem on CentOS Linux using NVIM v0.4.3 from NIX. Understand its not a priority for you though, I will use something else in the meantime! Cheers |
I can confirm that c4bedce is the cause of the issue and I'm like I dunno N% sure it's a neovim bug. I'll ask them. |
The good people of #neovim think there might be a neovim bug at play.
|
Brilliant to hear! Hopefully won't be anything to do on the vimspector side so! |
fixed it with @bfredl's help |
Describe the bug
Debugging is perfect in vim, when I try to do it in neovim I get the following error
To Reproduce
Open pythin file, place a breakpoing using f9, start deubber using f5
Vimspector config file:
Expected behavior
Debugger to work as per normal
Actual behaviour
Please include:
Environemnt
Version of Vimspector: (e.g. output of
git rev-parse HEAD
if cloned or thename of the tarball used to install otherwise)
'b7dee64'
Output of
vim --version
ornvim --version
which vim
orwhich nvim
::py3 pass
::py3 import vim
::checkhealth
Macos catalina 10.15.3
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: