Explanation for dap-repl and dap-console. #1186
Replies: 1 comment
-
I will answer 2. first because I suspect this should make things much clearer. However, not only does the client have to support this capability, the debug adapter has to do so as well. If this is not the case, the integrated terminal will not be connected to stdin / stdout, and you will not be able to type anything into it nor get any output. (More info on the integrated terminal and external console here.) Adapters which do not support the console may, for example, 'skip' inputs and display outputs in the REPL. Now, regarding 1./1.1 the exact details are dependent on the debug adapter. You should be able to find them in its documentation, for example, for codelldb (C/C++/Rust):
So yes, the repl will serve this 'dual purpose' for many other adapters as well. There should be debug adapters available for python that support the terminal. More specifically |
Beta Was this translation helpful? Give feedback.
-
What is the purpose of dap-repl and dap-console?
My understanding so far:
.scopes
,.continue
, etc (:h dap.repl.open()
).1.1 dap-repl, especially in the context of python: It also serves as a python REPL with access to the state of the program, ie. I can
print(VARIABLE)
whereVARIABLE
is part of the code I am currently debugging. Here, I also have a question: Does dap-repl serve this double purpose also for different languages?Beta Was this translation helpful? Give feedback.
All reactions