“New terminal” button in locked editor group causes new terminal to open in different editor group
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.61.0
- OS Version: macOS 11.6
Steps to Reproduce
- Create a locked editor group containing a terminal:
- Click the “New terminal” (+) button in the editor group header.
Result
The terminal opens in a different editor group and locks the group:
Expected result
The terminal should open in the same editor group, like so:
(This may be the same issue as #131156 but because it’s been closed I can’t comment in it.)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Integrated Terminal in Visual Studio Code
Use the Ctrl+Shift+` keyboard shortcut to create a new terminal. Use the View > Terminal or Terminal > New Terminal menu commands. From...
Read more >Switch focus between editor and integrated terminal
The problem with CTRL + ` is that it creates a new terminal even if one already exists. – Guss. Aug 23, 2020...
Read more >1. Inside the Terminal - Mac OS X For Unix Geeks, 4th Edition ...
It is also possible to open a new Terminal window (or tab) with the help of osascript, ... The other three groups of...
Read more >Documentation - iTerm2 - macOS Terminal Replacement
Click the Edit... button to configure the position, maximum size, ... set myTerm to (make new terminal) tell myTerm launch session \"Default\" end...
Read more >ThinManager 10 USer Guide
o Turning on the terminal and selecting the "Create New Terminal" option when ... You can click the Edit Server List button to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FWIW I can reproduce in both directions. Here I have an editor open on the left to verify that the behaviour isn’t dependent on the other editor being empty:
https://user-images.githubusercontent.com/30265160/137808679-2ff62bfd-5405-40b5-acb7-cf80539def02.mov
I can still reproduce this in the latest Insiders build (Version: 1.65.0-insider Commit: d09aeab62c1f93acf4a89b93e9a8a82419d6249a).