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 splitting the integrated terminal in both directions #56112

Open
mneil opened this Issue Aug 9, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@mneil

mneil commented Aug 9, 2018

I was unable to find another request like this. Most search results talk about wanting to dock the terminal/panel to the right or the bottom.

It would be nice if, when using the integrated terminal and splitting the terminal, I could choose to stack the terminals (one on top of the other) or put them side by side. Right now it seems like every time I split the terminal is puts the newest one to the right.

The option to have new terminals go underneath the last one would be great. I'm using a monitor rotated 90 degrees and I have a lot of real-estate at the bottom of the monitor where I can stack multiple terminals. I know it's not uncommon for developers to have 1 monitor rotated for development and I hope this would be helpful for other users as well.

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Aug 10, 2018

Member

This was a decision made when adding splitting to simplify the solution as well as the UX (by only allowing splitting horizontally when at bottom or vertically when at the right). I consider any additional movement on this blocked on #10121 (where we could potentially pull the panel out of the window).

Member

Tyriar commented Aug 10, 2018

This was a decision made when adding splitting to simplify the solution as well as the UX (by only allowing splitting horizontally when at bottom or vertically when at the right). I consider any additional movement on this blocked on #10121 (where we could potentially pull the panel out of the window).

@Tyriar Tyriar added this to the Backlog milestone Aug 10, 2018

@Tyriar Tyriar changed the title from Change panel layout in integrated terminal to Allow splitting the integrated terminal in both directions Aug 10, 2018

@ndbeals

This comment has been minimized.

Show comment
Hide comment
@ndbeals

ndbeals Aug 14, 2018

@Tyriar do you guys even have any plans for the Floating Window Request? It's sat on hold for over 2 years.

If nothing is going to happen there, then nothing is going to happen for this request either.

ndbeals commented Aug 14, 2018

@Tyriar do you guys even have any plans for the Floating Window Request? It's sat on hold for over 2 years.

If nothing is going to happen there, then nothing is going to happen for this request either.

@mneil

This comment has been minimized.

Show comment
Hide comment
@mneil

mneil Aug 14, 2018

I'm not even sure floating windows solve the problem. If I float the console and split it then I still have the same problem unless you add this functionality.

Or, if you expect me to open multiple windows each with a console I would be responsible for their layout. The ux would not be the same if I were left to resize and move multiple windows independently.

While I think it's related to pop out windows I don't know that it's dependent on that issue. For me, personally, I wouldn't even need more ui. A simple editor config to set whether the windows stack or or go side by side would be enough.

mneil commented Aug 14, 2018

I'm not even sure floating windows solve the problem. If I float the console and split it then I still have the same problem unless you add this functionality.

Or, if you expect me to open multiple windows each with a console I would be responsible for their layout. The ux would not be the same if I were left to resize and move multiple windows independently.

While I think it's related to pop out windows I don't know that it's dependent on that issue. For me, personally, I wouldn't even need more ui. A simple editor config to set whether the windows stack or or go side by side would be enough.

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Aug 14, 2018

Member

@ndbeals the issue mentions there's a technical limitation. I certainly hope we do soon as it will enable a lot of cool stuff.

@mneil this isn't technically blocked on it, but only when floating windows are supported, and you can pull the panel out, would we be able to justify spending time on this issue.

Member

Tyriar commented Aug 14, 2018

@ndbeals the issue mentions there's a technical limitation. I certainly hope we do soon as it will enable a lot of cool stuff.

@mneil this isn't technically blocked on it, but only when floating windows are supported, and you can pull the panel out, would we be able to justify spending time on this issue.

@FalseProtagonist

This comment has been minimized.

Show comment
Hide comment
@FalseProtagonist

FalseProtagonist Sep 30, 2018

I am trying to migrate from emacs and this is the second thing I tried to work out how to do.

How does vscode "think" about windows/frames/buffers? Is there a deep distinction with editors vs panels? Are windows/frames/buffers exposed such that I could write an extension to implement this?

FalseProtagonist commented Sep 30, 2018

I am trying to migrate from emacs and this is the second thing I tried to work out how to do.

How does vscode "think" about windows/frames/buffers? Is there a deep distinction with editors vs panels? Are windows/frames/buffers exposed such that I could write an extension to implement this?

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Sep 30, 2018

Member

@FalseProtagonist currently editors and panels and viewlets are all very different things, you wouldn't be able to write an extension to do this.

Member

Tyriar commented Sep 30, 2018

@FalseProtagonist currently editors and panels and viewlets are all very different things, you wouldn't be able to write an extension to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment