[1.21] You can have a restored settings tab and open a second settings tab #17070
Labels
Area-Settings
Issues related to settings and customizability, for console or terminal
Area-User Interface
Issues pertaining to the user interface of the Console or Terminal
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Tag-Fix
Doesn't match tag requirements
Product-Terminal
The new Windows Terminal.
Severity-Blocking
We won't ship a release like this! No-siree.
Milestone
Comments
DHowett
added
Issue-Bug
This comment was marked as off-topic.
This comment was marked as off-topic.
|
You can do this an infinite number of times! |
|
@zadjii-msft hah actually this applies to any newTab type:settings action. You can just keep doing it |
zadjii-msft
added
Area-User Interface
carlos-zamora
removed
the
Needs-Triage
zadjii-msft
added
the
Severity-Blocking
github-merge-queue bot
pushed a commit
that referenced
this issue
May 2, 2024
Re-add some machinery to special case settings tabs. When we're going to
persist a tab that only has a single settings pane in it, we'll now
promote that to the first-class "openSettings" action. This will allow
our other code in TerminalPage to route multiple settings tabs all to
the same tab.
This of course doesn't stop you from opening multiple settings tabs with
`{ "command": {"action": "newTab", "type": "settings"} }` actions. If we
did that, then that would prevent someone from having a settings pane in
the first pane, and a terminal to the right.
Closes #17070
microsoft-github-policy-service
bot
added
the
Needs-Tag-Fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows Terminal version
1.21.1011.0
Windows build number
No response
Other Software
No response
Steps to reproduce
Enable session restoration.
Open settings.
Close terminal.
Relaunch terminal.
Open settings again.
Expected Behavior
No response
Actual Behavior
The text was updated successfully, but these errors were encountered: