Vscode: Allow the user to resize the debug console input

Created on 12 Jun 2018  路  21Comments  路  Source: microsoft/vscode

Hi,

I'm not sure if some people could see this future useful but, it would be very nice to allow users to resize the debug console. We can resize the height of the panel , but not the the console itself.
Sometimes, I find that the console is a bit little small compared to the debug console output.
I know we can "shift+enter" to expand the console, but if I want to get the default size, I need to close Visual Studio Code and reopen it. It would be very nice if we could resize the console itself like we can resize the panel.

Here's a GIF demonstrating what feature to add :
vscode debug console

This feature should replace the default cursor for the resize arrows and should allow the user to resize the console. Maybe we can store the console size in the settings. With that information stored, when the user will reopen Visual Studio Code, the console will be exactly like the user want it.

Let me know if it's possible the add this feature.

Thanks!

*out-of-scope debug feature-request

Most helpful comment

This issue should _not_ be closed, it's the only thing wrong with VSCode right now. Shift + Enter makes the console larger but how do we make it smaller?? That's the main problem.

Often I open a new tab and want to paste code in it for a new file but for some reason if the debug console is open it will focus on there, and paste it into the debug console input instead making it really large and thus takes up all the space in the debug console. Then there's no way to revert it back to default size without restarting VSCode...

With attached mobile emulators open, a restart of VSCode can be annoying to say the least. Not to mention you lose all your undo history. Surely it can't be that difficult to implement this? It really causes much annoyance on a daily basis.

All 21 comments

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

This is a fair feature request thus leaving it open.
Yes, you are correct currently this is only possible via shift + enter for multiple lines

@isidorn Thank you !

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

This issue should _not_ be closed, it's the only thing wrong with VSCode right now. Shift + Enter makes the console larger but how do we make it smaller?? That's the main problem.

Often I open a new tab and want to paste code in it for a new file but for some reason if the debug console is open it will focus on there, and paste it into the debug console input instead making it really large and thus takes up all the space in the debug console. Then there's no way to revert it back to default size without restarting VSCode...

With attached mobile emulators open, a restart of VSCode can be annoying to say the least. Not to mention you lose all your undo history. Surely it can't be that difficult to implement this? It really causes much annoyance on a daily basis.

You make it smaller by pressing enter.

@isidorn Wow where've you been, that sure does work. Nobody in this thread has mentioned that yet and I even posted previously on Stackoverflow with zero answers. Thanks.

Sorry about that, this somehow slipped through my radar.

Glad that I'm not the only one that wants this feature haha.

In that case, should we re-open this issue?

I think it could be a good feature to have.
Yes I understand there's a workaround, but it could be a nice-to-have聽馃檪

@yanckst I think we don't need to re-open it since it can be resized using enter. I never would have guessed it would be enter, since I would have thought enter would have _added_ an extra line if anything. I was just trying things like right clicking looking through menus how to do it etc.

Yes, we will not re-open. Thanks for understanding.

hi @isidorn - It's difficult to reach the debug console input using mouse given it's just 1 line in height by default. I think we should still have this feature. Can we re-open ?

Hi. You can reach it by keyboard by pressing Cmd+J, or cmd+shift+y. The focus goes immediatly in the console and you can re-szie via shift+enter

Please re-open
It is difficult to move the mouse to a tiny line at the bottom of the screen
Shift-Enter will resize the input, but it will not persist between statements.
That means you have to enter it every time. If we could make it larger please, thanks.

@isidorn Wow where've you been, that sure does work. Nobody in this thread has mentioned that yet and I even posted previously on Stackoverflow with zero answers. Thanks.

where is the stack overflow question? Care to share?

@isidorn

how do you resize the whole pane debug console?

I tried:

control + command + up arrow or down arrow

but that only seems to work for the terminal.

SO: https://stackoverflow.com/questions/59903806/how-to-resize-debug-console-in-vs-code-with-a-keyboard-shortcut-while-using-pyt

You can use the mouse for the sash.
As for the keyboard, you can use the following commands:
Resize Pane Up, Resize Pane Down

Screenshot 2020-01-27 at 10 58 10

You can use the mouse for the sash.
As for the keyboard, you can use the following commands:
Resize Pane Up, Resize Pane Down

Screenshot 2020-01-27 at 10 58 10

so there is no keyboard short cut? Why does the shortcut I suggested only work for the terminal pane?

You can assign a custom keyboard shortcut for any command.
Preferences > Keyboard Shortcut

That shortcut is probably only assigned by the terminal. @Tyriar would know more

@isidorn yes you're right.

This should probably eventually be a more generic command that does it for the focused view, rather than just the terminal. Maybe something to consider after the view refactors are further along?

@Tyriar agree. So fyi @sbatten

Was this page helpful?
0 / 5 - 0 ratings