Replies: 1 comment
-
Well, I've figured out part of the answer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Here is my nvim-dap.lua file:
I also have which-key configured. If I open a python file and look at the key_bindings, <Leader>dc
and <Leader>dt are not defined and they don't work (ie its not a which-key problem)
If I issue, this command in the python file:
:lua require'dap'.set_log_level('INFO')
then which-key does show the mappings. <Leader>dt appears to work and a 'B' shows up in the margin. <Leader>dc kind of works in that an arrow appears in the margin replacing the B but none of the UI elements open as expected.
When I repeated the exercise I got this crash:

Lazy shows that nvim-dap, nvim-dap-python, nvim-dap-ui and nvim-io are installed but not loaded.
Mason shows that debugpy is installed.
This is on an old Ubuntu 20.04 machine and I have both python2 and python3 installed. /usr/bin/python is a symbolic link to /usr/bin/python3.
Can anyone explain what is happening and how I can get the dap-ui to show up?
Steve
Beta Was this translation helpful? Give feedback.
All reactions