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
joaomoreno opened this issue
Apr 26, 2016
· 3 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priorityverifiedVerification succeeded
joaomoreno
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
important
Issue identified as high-priority
labels
Apr 26, 2016
I also see this behavior in stable 1.0.0 and I think it was like this forever.
I do not think it is imporant and I also think dup of #5831
Let me know if you disagree and I will reopen
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 issuesimportantIssue identified as high-priorityverifiedVerification succeeded
Testing #4954
.js
file.Debugging should stop immediately since the file doesn't do anything. It never does! 👎
The text was updated successfully, but these errors were encountered: