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
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
If you have multiple debug configurations, this works:
Select first debug config on the debug side bar
Click Debug -> Start Without Debugging
Select second debug config on the debug side bar
Click Debug -> Start Without Debugging
Against the Start Without Debugging menu entry, it says the shortcut key is Ctrl+F5. Yet if you perform the same steps above using F5, the second debug configuration will not launch.
I think this is because the keybind has !inDebugMode as a condition, but I think this is confusing and unwanted. If a menu entry is enabled, and shows a shortcut key, that shortcut key should do the same thing as clicking on the menu entry.
The text was updated successfully, but these errors were encountered:
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Sep 20, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
If you have multiple debug configurations, this works:
Debug
->Start Without Debugging
Debug
->Start Without Debugging
Against the
Start Without Debugging
menu entry, it says the shortcut key isCtrl+F5
. Yet if you perform the same steps above using F5, the second debug configuration will not launch.I think this is because the keybind has
!inDebugMode
as a condition, but I think this is confusing and unwanted. If a menu entry is enabled, and shows a shortcut key, that shortcut key should do the same thing as clicking on the menu entry.The text was updated successfully, but these errors were encountered: