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
roblourens opened this issue
Jul 29, 2018
· 1 comment
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
but recently f8 always triggers 'go to next problem' even in debug mode, unless the editor isn't focused. I'm not sure how precedence is supposed to work when two keybindings both apply, maybe the keybindings are registered in a different order now. But I also noticed that 'debugState' and if I use "when": "debugState != 'inactive'" instead, it seems to work all the time?
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
Jul 30, 2018
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
I've had this keybinding forever,
but recently f8 always triggers 'go to next problem' even in debug mode, unless the editor isn't focused. I'm not sure how precedence is supposed to work when two keybindings both apply, maybe the keybindings are registered in a different order now. But I also noticed that 'debugState' and if I use
"when": "debugState != 'inactive'"
instead, it seems to work all the time?The text was updated successfully, but these errors were encountered: