Skip to content
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

Closed
1 task done
isidorn opened this issue May 6, 2016 · 5 comments
Closed
1 task done

Setting for revealing the debug console #6159

isidorn opened this issue May 6, 2016 · 5 comments
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented May 6, 2016

We have introduced a setting internalConsoleOptions in launch.json to change the behavior of automatic revealing of the debug console. Verify this setting is easy to find, use and works as expected.

@isidorn isidorn added debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item labels May 6, 2016
@isidorn isidorn added this to the May 2016 milestone May 6, 2016
@mattflix
Copy link

mattflix commented May 13, 2016

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 internalConsoleOptions setting, nor its possible values, seem to be documented by the intellisense within the launch.json file. In fact, the intellisense there seems to be pretty messed up and incomplete in version 1.1.0, vesus what it was in 1.0.0 -- I would not known of the existence of internalConsoleOptions were it not for this issue.

@isidorn
Copy link
Contributor Author

isidorn commented May 13, 2016

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.
If you want to get this behavior before I think we will anounce our alpha channel soon, so stay tuned for that.

@mattflix
Copy link

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.

@isidorn
Copy link
Contributor Author

isidorn commented May 13, 2016

Yeah it changed, let me search for the issue... Here it is #4045
Yeah I also wanted that esc behavior and was fighting for it, but we have too many things binded to esc at the moment. So what works for me is esc when console has focus - closes it
And ctrl + J always toggles it - which is what I use in the end for my day to day development

@egamma egamma mentioned this issue May 23, 2016
87 tasks
@sandy081
Copy link
Member

Tested.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Projects
None yet
Development

No branches or pull requests

3 participants