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
I am currently implementing something akin to an »auto-attach« feature for vscode-perl-debug. When I call vscode.debug.startDebugging I do not have a good name for the debug session yet, but once a connection to the debugger is established, I can come up with a better one.
I do have control over the thread name, but in case of Perl, there is only ever one thread, and I'd rather not have session name and also thread name in the user interface, #69752.
(Some way to make vscode use the thread name of the single thread in place of the poorly auto-generated session name would work for me.)
The text was updated successfully, but these errors were encountered:
I am currently implementing something akin to an »auto-attach« feature for
vscode-perl-debug
. When I callvscode.debug.startDebugging
I do not have a good name for the debug session yet, but once a connection to the debugger is established, I can come up with a better one.Unfortunately the
DebugSession.name
property isread-only
and there does not seem to be an alternative to set it post-launch. https:/Microsoft/vscode-node-debug/blob/d490a306164fd086e7e792dec858b1d36a879871/src/node/extension/autoAttach.ts#L62 also uses an awkward name likeAuto attached (123)
it seems.I do have control over the thread name, but in case of Perl, there is only ever one thread, and I'd rather not have session name and also thread name in the user interface, #69752.
(Some way to make vscode use the thread name of the single thread in place of the poorly auto-generated session name would work for me.)
The text was updated successfully, but these errors were encountered: