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

Allow both console and output to be displayed simultaneously #3597

Closed
bgashler1 opened this issue Mar 1, 2016 · 7 comments
Closed

Allow both console and output to be displayed simultaneously #3597

bgashler1 opened this issue Mar 1, 2016 · 7 comments
Assignees
Labels
ux User experience issues

Comments

@bgashler1
Copy link
Contributor

See #1875 (comment)

Whenever the console updates, he loses his output window.

@isidorn
Copy link
Contributor

isidorn commented Mar 1, 2016

This is fixed in the march release of vscode, console is not so spammy and only reveals itself on new debug launch.
From what the user described his main problem is that the console pops up when not needed. Not that he needs to look at console and output at the same time

@mredbishop or did I understand wrongly? You can tryout the march insiders vscode, or the march update next week and let us know if this behavior improved for you

Let me know what you guys think and I can reopen

@isidorn isidorn closed this as completed Mar 1, 2016
@mredbishop
Copy link

Actually, for me it's the reverse. My debug is pretty spammy, so when I'm running a task and viewing the output window for the details it keeps jumping back to the debug window. I would really like to be able to see both as they are both important but failing that I would like an option to turn off bringing debug and/or output to the front when they updates.

@mredbishop
Copy link

P. S. I'll try the insider update anyway and see how that differs.

@isidorn
Copy link
Contributor

isidorn commented Mar 2, 2016

If you understand you correctly, you do not have the reverse situation. Debug will no longer jump back to front when updates. Please try out the insider update and let us know what you think.

@mredbishop
Copy link

Will do, cheers :)

On Wed, 2 Mar 2016 at 09:28 Isidor Nikolic [email protected] wrote:

If you understand you correctly, you do not have the reverse situation.
Debug will no longer jump back to front when updates. Please try out the
insider update and let us know what you think.


Reply to this email directly or view it on GitHub
#3597 (comment).

@mredbishop
Copy link

Awesome, this does exactly what I was after. Thanks :)

On Wed, 2 Mar 2016 at 10:01 Edward Bishop [email protected] wrote:

Will do, cheers :)

On Wed, 2 Mar 2016 at 09:28 Isidor Nikolic [email protected]
wrote:

If you understand you correctly, you do not have the reverse situation.
Debug will no longer jump back to front when updates. Please try out the
insider update and let us know what you think.


Reply to this email directly or view it on GitHub
#3597 (comment).

@isidorn
Copy link
Contributor

isidorn commented Mar 3, 2016

Glad to hear :)

@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
ux User experience issues
Projects
None yet
Development

No branches or pull requests

3 participants