-
Notifications
You must be signed in to change notification settings - Fork 29.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split terminal when using a compound debug configuration #69619
Comments
(Experimental duplicate detection)
|
@vscodebot you try but as usual you don't help.
|
Okay so @vscodebot mentioned #47265 which according to my reading of it should make it so that setting a This has not been something that I was able to demonstrate, and also this field seems to not be free form, but a closed set of values instead. My repro here: https://github.com/TomasHubelbauer/vscode-compound-debug-split-terminal |
Actually I think I might have duplicated #68123 which I did not find when searching. @markfinlabs do you feel like your issues covers this use case as well? If yes, I'll be happy to close mine. |
Yes I believe so. My use case is multiple (in my case more than 2) launch configs in integrated terminals and I am keen to see them side-by-side in a split terminal following starting a compound launch configuration. Which I believe covers your use case as well. |
When using a compound debug configuration, each task gets its own terminal. I can split these terminals manually, but I don't think there is a way to get these terminals side-by-side. And I don't think this is doable with an extension either. There is a split terminal API proposal in #45407 but applying that to both of the task terminals would just give me two extra empty terminals. I am looking for a way to get the two task terminals side-by-side in one integrated terminal pane so there is no need to switch between them. The way I'd like to see this done is an extra field in the debugger configuration which says whether the terminals should start standalone or split. I am not sure how this would deal with 3+ configurations, but that seems to be niche enough to not have to worry about it until an issue is raised.
The text was updated successfully, but these errors were encountered: