jyapayne/vimspector
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Neovim 0.4 doesn't work for debugpy because it is missing features

Browse source
This commit is contained in:
Ben Jackson 2020-02-01 00:06:49 +00:00
commit 44efc0a1b3
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -173,6 +173,7 @@ neovim doesn't implement some features Vimspector relies on:
the output window's current output. the output window's current output.
* Prompt Buffers - used to send commands in the Console and add Watches * Prompt Buffers - used to send commands in the Console and add Watches
* Balloons - used to display the values of variables when debugging. * Balloons - used to display the values of variables when debugging.
* Environment variables when laucnhing debugee in embedded terminal.
Workarounds are in place as follows: Workarounds are in place as follows:
@ -185,6 +186,9 @@ Workarounds are in place as follows:
There is no workaroud for the lack of balloons; you'll just have to use There is no workaroud for the lack of balloons; you'll just have to use
`:VimspectorEval` or `:VimspectorWatch`, or switch to Vim. `:VimspectorEval` or `:VimspectorWatch`, or switch to Vim.
The only workaround for the missing environment variables feature is to use
neovim master (it doesn't work in neovim 0.4).
## Language dependencies ## Language dependencies
The debug adapters themselves have certain runtime dependencies: The debug adapters themselves have certain runtime dependencies:
@ -727,6 +731,10 @@ session.
### Alternative: Use debugpy directly ### Alternative: Use debugpy directly
*** NOTE: This solution does not work in NeoVim 0.4 due to missing environment
variables support when launching a terminal. Do not raise issues about this if
you are using NeoVim 0.4. ***
If you can't get a node 10 environment set up for whatver reason, then you can If you can't get a node 10 environment set up for whatver reason, then you can
avoid that issue by using `debugpy` (formerly `ptvsd`) directly. avoid that issue by using `debugpy` (formerly `ptvsd`) directly.