Stop or kill the session or simply continue until the process terminates
Delete the terminal buffer with bwipeout! or bd! or with the nvim api.
ls! - the terminal buffer is wiped
Re-start the previous session
ls! - the terminal buffer is re-created (somehow) but the terminal win_cmd is never called again or re-run again.
Expected Result
The terminal command should be re-run, the terminal buffer should be cleaned up correctly, and possibly let the user control how to delete the buffer i.e introduce a new property in the config which similarly to the cmd, is responsible for cleaning up the terminal buffer or / and window.
Actual Result
The terminal win_cmd is not run again, the buffer is re-created, somehow but not shown (looking at ls! i can see it is there, with a new id/handle)
Debug adapter definition and debug configuration
The configuration does not really matter as long as it is supporting the integrated terminal option, can repro with c and cpp configurations too.
Debug adapter version
master
Steps to Reproduce
Expected Result
The terminal command should be re-run, the terminal buffer should be cleaned up correctly, and possibly let the user control how to delete the buffer i.e introduce a new property in the config which similarly to the cmd, is responsible for cleaning up the terminal buffer or / and window.
Actual Result
The terminal win_cmd is not run again, the buffer is re-created, somehow but not shown (looking at ls! i can see it is there, with a new id/handle)