-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All program launches imply debugging in Eclipse 4.30 #1424
Comments
acarstoiu
changed the title
All program launches imply debugging
All program launches imply debugging in Eclipse 4.30
Dec 7, 2023
Can you please open a separate issue about the fact that the DAP output console is shown by default? I don't think it's a behavior we want to keep. |
acarstoiu
changed the title
All program launches imply debugging in Eclipse 4.30
All program launches imply debugging in Eclipse _4.30_
Dec 7, 2023
acarstoiu
changed the title
All program launches imply debugging in Eclipse _4.30_
All program launches imply debugging in Eclipse 4.30
Dec 7, 2023
Have you identified whether there is a missing setting in the Debug Adapter configuration to skip debug? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running the latest Wild Web Developer 1.3.3.202311211923 on Eclipse 4.30, which I've just upgraded. Following this switch from Eclipse 4.29 to 4.30 I had the unpleasant surprise too see that running a JS file is identical to debugging it. There's no difference between choosing "Run As" -> "Node program" and "Debug As" -> "Node program":
Combined with the fact that the debugging itself clears the program's output from the Console view and seemingly replaces it with debug tracing like
it's really annoying. There are actually two consoles, the one with the program's output is hidded by another containing the debug adapter output.
The text was updated successfully, but these errors were encountered: