-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Please bring back ability to move terminal to the RIGHT of the editor #142075
Comments
I'd like to know if this is possible too. Previously I would have my layout like this:
Depending on whatever other applications I happened to be working on, I had a keyboard shortcut to toggle the terminal to/from the bottom/side so it would change to this:
This workflow worked great for me. Now it seems like there's only the ability to move the terminal into the "side panel", which seems like it's only ever the opposite side as the side bar. I can't have the "side bar" and the "side panel" on the same side. |
@gotofritz what happened is that the devs got sloppy and they just took that functionality away. You can try to run it by hand from the commands panel and you'll get
They came up with this sidebar thing without thinking twice about all the workflows that they are breaking with this nonsense. |
What makes this even worse is that you can maximize the Panel (the thing that's in the bottom by default and held all your views including the terminal) but you can't maximize the side panel! What I've been doing is that I had my terminal on the right side and I could toggle between invisible, visible, and maximized with a keyboard shortcut. It is very useful if you're running tmux for exmaple (or things like mc) in your terminal and you quickly want to jump between coding and doing stuff in a maximized terminal. Whoever did this to VS Code please undo it. |
@gotofritz my suggestion is to opt-out of automatic upgrades and downgrade to |
@adam-arold Sure, but that would only be delaying the inevitable for another month or so, wouldn't it? I'd rather be part of the conversation. Perhaps if enough users let them know their fiddling is unhelpful, they may revisit their roadmap! |
I agree with that, but it is broken now and I want to work now. I can't wait for them to fix this, unfortunately. |
cc @lychung7 |
feedback here is noted... please continue discussion in this issue #141349 |
I have always had the panel vertically, to the right of the editor, between editor and sidebar (which I keep to the right). Now with the latest version of insiders it was automatically arranged horizontally. When I right click on the title bar, the only option is a toggle between "Move views to the side" and "Move views to Panel". First of all - what does it even mean? I am trying to move the Terminal, not some weird thing called "views". And what does it mean "move to the Panel"?? Sounds like some weird, unintuitive abstraction. I don't think it helps at all.
Most importantly, when I move the Term... sorry, the "Views" to the side, it only allows me to the move it to the left. Why remove the ability to move it to the right? It's something that we were able to do for years. What problem are you trying to solve?
And if I move the Term... sorry, the "Views" to the side, then hide it... how do I get it back? The old CMD-J brings up an empty space where the Terminal used to be... the Te.. "Views" is nowhere to be seen. Can you show me a use case where that kind of behaviour would be useful?
If I then do "Terminal > New Terminal" I get a terminal - as a editor tab. So YET ANOTHER place for a terminal. It's not the same terminal I had before - that presumably is still around. Somewhere.
AAAAARGGGH
I am confused by the changes, which seem totally unnecessary and do not solve any problems. And I am irritated because I am no longer able to use VSC the way I have for years, for what to me looks like an arbitrary decision.
I hope future iterations will bring some of the old functionality back, while avoiding unnecessary abstractions. Thanks.
The text was updated successfully, but these errors were encountered: