starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Open Previous Layout opens with an additional new window as well #22834

New Issue
Open
opened 2026-01-31 08:24:49 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:24:49 +00:00
Owner
Copy Link

Originally created by @cicu812 on GitHub (Feb 1, 2025).

Windows Terminal version

Windows Terminal Preview Version: 1.22.3232.0

Windows build number

Win32NT 10.0.26100.0 Microsoft Windows NT 10.0.26100.0

Other Software

No response

Steps to reproduce

On initial launch, no other Windows Terminals open, Start Menu/Task bar select Windows Terminal.

Context:

Settings>Startup provides only two relevant options regarding how Windows Terminal opens with respect to this consistent windowing issue:

  1. When Terminal starts: What should be shown when the first terminal is created; which dropdown provides for the selection of one of two available options:
  • "Open windows from a previous session" (which is what I prefer and have set)
  • "Open tab with the default profile"
  1. New instance behavior: Controls how new terminal instances attach to existing windows which dropdown provides for one of three available options:
  • Create a new window (which is what I prefer and have set)
  • Attach to the most recently used window
  • Attach to the most recently used window on this desktop

Expected Behavior

Open just the Previous Window layout where my splits are are preserved; not an extra Windows Terminal on a single click to launch initially. I would expect this extra window only in the event I had yet once again clicked to select Windows Terminal anew to launch another new window for Windows Terminal, but I don't expect that a single click should launch both previous layout and a new Windows terminal (two separate Windows Terminals).

Actual Behavior

On initial launch, that is, no other Windows Terminals are open and resident in memory, consistently opens Previous Window Layout (splits preserved) WITH an additional AND NEW Windows Terminal also opened behind the previous layout, for a total of two Windows Terminals. (I only expect the one previous layout opening on a single click of Windows Terminal. Only given, Windows Terminal re-select and click, do I expect an additional new Windows Terminal window, should I again, subsequently, select and click.

It seems to me the issue is the conflation of a new window with the opening of previous layout on single-click initial launch where only the previous layout should be expected. Subsequent intended re-click(s) of Windows Terminal select-launch should only then open new windows for Windows Terminal, as needed, but not uninitiated from the user's perspective on initial launch as it now appears unexepectly.

Thank you for your valuable time! All the best.

Originally created by @cicu812 on GitHub (Feb 1, 2025). ### Windows Terminal version Windows Terminal Preview Version: 1.22.3232.0 ### Windows build number Win32NT 10.0.26100.0 Microsoft Windows NT 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce On initial launch, no other Windows Terminals open, Start Menu/Task bar select Windows Terminal. Context: Settings>Startup provides only two relevant options regarding how Windows Terminal opens with respect to this consistent windowing issue: 1) `When Terminal starts: What should be shown when the first terminal is created`; which dropdown provides for the selection of one of two available options: - "**Open windows from a previous session**" (which is what I prefer and have set) - "Open tab with the default profile" 2) `New instance behavior: Controls how new terminal instances attach to existing windows` which dropdown provides for one of three available options: - **Create a new window** (which is what I prefer and have set) - Attach to the most recently used window - Attach to the most recently used window on this desktop ### Expected Behavior Open just the Previous Window layout where my splits are are preserved; not an extra Windows Terminal on a single click to launch initially. I would expect this extra window only in the event I had yet once again clicked to select Windows Terminal anew to launch another new window for Windows Terminal, but I don't expect that a single click should launch both previous layout and a new Windows terminal (two separate Windows Terminals). ### Actual Behavior On initial launch, that is, no other Windows Terminals are open and resident in memory, consistently opens Previous Window Layout (splits preserved) WITH an additional AND NEW Windows Terminal also opened behind the previous layout, for a total of two Windows Terminals. (I only expect the one previous layout opening on a single click of Windows Terminal. Only given, Windows Terminal re-select and click, do I expect an additional new Windows Terminal window, should I again, subsequently, select and click. It seems to me the issue is the conflation of a new window with the opening of previous layout on single-click initial launch where only the previous layout should be expected. Subsequent intended re-click(s) of Windows Terminal select-launch should only then open new windows for Windows Terminal, as needed, but not uninitiated from the user's perspective on initial launch as it now appears unexepectly. Thank you for your valuable time! All the best.
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 08:24:50 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Author-Feedback Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22834
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?