You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Would it work to chain tasks, or start debugging through a task? You could also specify to use the integrated terminal for the debugger instead of starting a new one. Or are you less looking for this type of work-around and more just want me to put this as a feature request to consider?
Hi @eleanorjboyd, I suppose it may be possible to start debugging through a task using no-config debugging, which I just found out about and haven't had the chance to try it; it's still only in Insiders releases as far as I'm aware. Or did you mean something else?
Regarding specifying to use the integrated terminal for the debugger instead of starting a new one, I've spent a few hours trying to find out how to do this, but it doesn't seem to be possible (other than using the new no-config debugging). If you know how to do it please tell me.
Unless there is another easy way to do these things that I don't know, even with the no-config debugging, I think it would be a nice feature to be able to specify the shell commands in debugging configurations which can be started from the GUI.
looping in @connor4312 since he is the expert on debugging and might have an idea to make this work.
In regards to no-config debugging it is out on the most recent stable version of the python debugger extension so you should be able to use it now, let me know if you are not able to as this may be a different problem
I don't have much apetite to try to make debug use the same terminal as the prelaunch task. That's a bit hard for a number of reasons. However you may want to check out the presentation property of tasks that lets you configure if/when the task terminal gets revealed, which would allow it to start less obtrusively in the background.
For example, environment setup commands.
It's possible to add prelaunch tasks, but the debugger does not run in the same terminal.
The text was updated successfully, but these errors were encountered: