-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Auto hide panel #10952
Comments
Related: #3742 |
Hi @Tyriar - I saw that you closed several duplicate issues related to this. Is there an ETA for adding this functionality? Thanks. |
No ETA, #2806 will probably get looked at before this one. |
+1 It would be also nice to have an option to show terminal only when underlying shell exited with code other than 0 (zero) OR something was printed to stderr. E.g. i'm starting CMake build in shell, but i don't want to see terminal until it requires my attention: for example, a compilation error occurred, warning was printed (normally to stderr) or shell failed to execute build in some other way. |
+1 |
I would also want this feature. +1 |
+1 |
1 similar comment
+1 |
+1 I was just working with Angular and...well.. this happened. |
+1 |
1 similar comment
+1 |
+1 - Is this still pending since 2016 or am I missing a fix? |
+1 |
Considering writing a plugin for this. My biggest problem with the VSC interface in general is the lack of feedback on actions. Make a Git pull, start a Vagrant box, etc, and if you don't have the Terminal already open and ready (and manually switch to the new Terminal tab every tool run generates), you get absolutely zero feedback. It's quite frustrating to have to go looking for the outcome of actions taken. |
@GregJPreece any luck? |
+1 Please add this feature :) |
+1 |
FYI while waiting for this add-on, the shortcut ctrl + ` should open/close the terminal |
+1 |
close does not suit when you've opened VSC from a parent directory as every time you should: |
https://marketplace.visualstudio.com/items?itemName=venryx.vscode-vtools does a pretty good job working around the lack of this in the core product IMO. Has the occasional bug, but works well enough on a day-to-day basis. |
Works well. However, once the bottom bar/terminal is hidden, is there a shortcut to open that same terminal again without having to do to Terminal -> New Terminal? |
|
You can just do ctrl+` |
Afaik not on Linux, there the combo is |
You must be right. I'm on linux myself so I probably changed that hotkey. My bad. |
vscode-vtools doesn't seem to solve this for me; if I run a build command which opens the terminal, executes a single command, and then stops, continuing to type in my existing code panel doesn't close the terminal. Since the terminal never had focus, it doesn't count as losing focus? I have to click inside the terminal, then click back into the code to make the panel disappear, which is almost worse than having to press ctrl+` twice to put focus into the terminal, then close it. I want to run a build command either without showing the output, or showing and then hiding the panel afterward without having to press anything extra. I just don't need to see the build output most of the time for my purposes, and I have a small laptop screen where every inch of vertical space is important. UPDATE: I re-read the docs and learned there's a task option to never show the terminal in the first place. This is what I wanted! Docs here. Add this inside the task.json:
|
+1 |
I'm just wondering why this is still open. Should have a built in option or let the extensions do the show. |
I just tried it. It does exactly what I want! Thank you! |
For keyboard shortcut users, here's my workaround. Goal: to close all panels/sidebars and focus back on the editor on keystroke. If you have a panel (terminal, console, linter, etc) or a sidebar (git, file explorer, etc) open or in focus, pressing the keybinding will focus your cursor back to the active editor tab and close all panels and sidebar. Steps:
{
"key": "escape",
"command": "macros.switchToEditorHidePanes",
"when": "panelFocus || terminalFocus "
},
{
"key": "escape",
"command": "macros.switchToEditorHidePanes",
"when": "editorIsOpen && sideBarVisible"
},
{
"key": "escape",
"command": "macros.switchToEditorHidePanes",
"when": "activePanel"
},
|
This extension do this. |
@jonyeezs I love the use of "ESC" to do this but I think your solution is missing the second part: restoring the terminal when you press ESC inside the editor, so we can have the full round-trip. Have you one a solution for that? |
I just open terminal as per normal keyboard shortcut. So no single shortcut to rule them all |
+1 |
One of the problems with how auto hide is implemented in Visual Studio is that the terminal will not auto hide when my cursor is above it, even if I have started typing in the editor. Please do not add that annoying behavior to VSCode. |
Would love something like this |
Please add this or the ability to set one of the following: Disable Autoshow, Disable Logging, Location="none" (or similar). |
Yes, I would like a simple way to hide the 'Problems' panel (problems, errors, output, terminal tabs), because it takes too much monitor estate and it drives me crazy to have to hide it after almost every operation. |
Still looking for this on the year of 2024 :) |
Just do what QtCreator does: hide the bottom window with the ESC key. The way they do it is perfect; they figured it out long ago. |
Similar to behavior in Visual Studio, is there a way we could get the terminal to show/hide automatically? Leaving some sort of tab at the bottom of the screen?
It opens when:
It hides when:
Ex: I'm working on an Angular 2 application using the angular-cli build tool. When I'm writing code or clicking through the UI I don't particularly care about what's displaying in the terminal. But as soon as I save my changes and the build process starts, I DO want to quickly see what the current state of the build is. So after saving a file, when the CLI tool starts writing to the terminal, it would pop-up from the bottom, and as long as my mouse isn't hovering over it, it will hide again after several seconds of inactivity.
The text was updated successfully, but these errors were encountered: