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

The close all tab warning could prompt the user to enable "persist window layout" if it's disabled #19652

New Issue
Open
opened 2026-01-31 06:49:45 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:49:45 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Apr 6, 2023).

An off-the-cuff suggestion from @chendrixson

If the user doesn't have "remember window layout" enabled, and they close more than one tab, maybe we could add a checkbox to that dialog to ask them if they want to turn that setting on.

Thoughts:

  • Turning the setting on and saving the window layout at this point in teardown might be tricky
  • Is there a way for users to say "No I absolutely do not want to save the layout and stop asking?" Does that even matter? It's just a checkbox...
  • Is there a way to remember the layout once, like, for just the next launch?
  • How does this play with the "close multiple panes" warning / multiple processes?
  • Should we put this in the quit dialog? (we should put it there too)
Originally created by @zadjii-msft on GitHub (Apr 6, 2023). _An off-the-cuff suggestion from @chendrixson_ If the user doesn't have "remember window layout" enabled, and they close more than one tab, maybe we could add a checkbox to that dialog to ask them if they want to turn that setting _on_. Thoughts: * Turning the setting on and saving the window layout at this point in teardown might be tricky * Is there a way for users to say "No I absolutely do not want to save the layout and **stop asking**?" Does that even matter? It's just a checkbox... * Is there a way to remember the layout _once_, like, for just the next launch? * How does this play with the "close multiple panes" warning / multiple processes? * Should we put this in the quit dialog? (we should put it there too)
claunia added the Issue-FeatureArea-SettingsProduct-TerminalArea-UserInterface labels 2026-01-31 06:49:45 +00:00
claunia commented 2026-01-31 06:49:46 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Apr 6, 2023):

I think that the user himself should think about saving the layout or doing nothing. I never save, because once I saved the current KDE session and then could not log in due to the failure of one of the widgets, then I had to log in to TTY and manually edit the xml files.

@237dmitry commented on GitHub (Apr 6, 2023): I think that the user himself should think about saving the layout or doing nothing. I never save, because once I saved the current KDE session and then could not log in due to the failure of one of the widgets, then I had to log in to TTY and manually edit the xml files.
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 Area-Settings Area-UserInterface Issue-Feature Product-Terminal
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#19652
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?