Add "Disconnect single session" command

[jrieken]

This needs some explanation and what I do isn't as wrong as the title suggests: I have ~/Code/vscode for our sources and I have ~/Code/_samples/dummy-extension in which I try out and test API. The extension is sym-linked into ~/.vscode-oss-dev/extensions. This allows me to make changes in the extension and VS Code itself and easily test things

• from vscode run/debug VS Code (it debugs everything: main, renderer, ext-host
• in dummy-extension set a breakpoint in some extension code (where else)
• from dummy-extension attach to extension host (to apply those breakpoints)
• run the code, hit the breakpoint, and step in/out/over
• 😕 the windows randomly change focus, both are debugging the extension host (naturally)

I don't know how you would implement this but the window at which breakpoint was most recently hit should be the active one

Screen.Recording.2022-08-19.at.13.09.47.mov

[roblourens]

Would you consider using a multiroot workspace? That workflow should work. Otherwise I guess I'd have to implement some locking mechanism through the shared process, which sounds like a great bug generator.

[roblourens]

Or do you want to just not attach to the extension host process in the vscode window?

[jrieken]

Would you consider using a multiroot workspace?

No

[roblourens]

I'd recommend not attaching to the EH process in the vscode window (you will need to change launch.json for this or add your own config which you could do in a workspace) or you can disable debug.focusWindowOnBreak in the vscode window. I think that doing exactly what you want will be really complicated.

[jrieken]

I'd recommend not attaching to the EH process in the vscode window

Can I disconnect from the EH while still using the "big" launch config? E.g launch normally and from time to time just disconnect the EH?

[roblourens]

Normally you would be able to but the compound has "stopAll": true so that if you disconnect from one, you will be disconnected from all. This is just so you don't have to click disconnect 5 times or find the "right" session with a stop button that will actually kill the app.

[jrieken]

Is there a change for an alternative disconnect action? Given launch configs are shared and sits inside the repo I cannot just put my personal changes on top. In addition, stopAll is what I want but not exclusively

[roblourens]

I think a "Disconnect Single Session" command would make sense that overrides stopAll

[roblourens]

and sits inside the repo I cannot just put my personal changes on top

I use the vscode repo in a workspace with a single folder, I often have some custom workspace settings or launch configs

[VSCodeTriageBot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!