-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Setting for revealing the debug console #6159
Comments
Could you at least mention what setting will restore the old 1.0.0 behavior (which seemed to be to reveal upon launch)? I do not like the new default behavior in 1.1.0 (which does not reveal the console). Btw, the new |
Hi @mattflix thanks for constantly providing useful feedback. However this is not documented because it is in the may - release which means it will be made public early June (yeah the naming is a bit confusing). Thus you should get nice inteli-sense and be able to configure debug console behavior with the next vscode release 1.2. |
Okay thanks, will look forward to that. Am I crazy, or did the debug console reveal behavior change between 1.0.0 and 1.1.0? (I swear I didn't have to constantly manually bring back the console on every launch, and now I do.) Btw, I would love the ability to simply hit the Escape key to toggle the console shown/hidden state (like it works in Chorme DevTools). I tried, but could not make a VS Code key mapping do this for me. |
Yeah it changed, let me search for the issue... Here it is #4045 |
Tested. |
We have introduced a setting
internalConsoleOptions
inlaunch.json
to change the behavior of automatic revealing of the debug console. Verify this setting is easy to find, use and works as expected.The text was updated successfully, but these errors were encountered: