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

Changing conhost settings without writing them permanently to registry/shortcut #20444

New Issue
Open
opened 2026-01-31 07:14:02 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:14:02 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Sep 6, 2023).

Originally discussed here.

Description of the new feature/enhancement

In previous Windows versions, when you open console properties and change something, it was always asking you "Apply properties to current window only" / "Save properties for future windows with same title" / "modify shortcut that started this window":

image
image

It was quite useful: if you need to experiment with console settings (and if you develop non-trivial console apps, affected by those settings - you do), you just choose "current window only", and all your silly experiments disappear when you close this console window.

But in newer Windows versions that useful confirmation was removed for unknown reasons and the properties are now always quietly saved as if "save for future windows with the same title" or "modify shortcut that started this window" was chosen, meaning that all your silly experiments are now persisted immediately and you have to undo them later manually like an idiot. It is no longer possible to make changes for the current session only.

Proposed technical implementation details (optional)

"Modify" and "Save" actions should be clearly separated.
One option is to simply restore the feature from pre-Windows 7 codebase.
Another one is to rework it to make it more obvious.

Originally created by @alabuzhev on GitHub (Sep 6, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> Originally discussed [here](https://github.com/microsoft/terminal/issues/15458#issuecomment-1572902203). # Description of the new feature/enhancement In previous Windows versions, when you open console properties and change something, it was always asking you "Apply properties to current window only" / "Save properties for future windows with same title" / "modify shortcut that started this window": ![image](https://github.com/microsoft/terminal/assets/11453922/b843f31d-b66a-4d97-8862-490d4768fa8b) ![image](https://github.com/microsoft/terminal/assets/11453922/5657a39a-813b-482e-be68-185adef09d3b) It was quite useful: if you need to experiment with console settings (and if you develop non-trivial console apps, affected by those settings - you do), you just choose "current window only", and all your silly experiments disappear when you close this console window. But in newer Windows versions that useful confirmation was removed for unknown reasons and the properties are now always quietly saved as if "save for future windows with the same title" or "modify shortcut that started this window" was chosen, meaning that all your silly experiments are now persisted immediately and you have to undo them later manually like an idiot. It is no longer possible to make changes *for the current session only*. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> "Modify" and "Save" actions should be clearly separated. One option is to simply restore the feature from pre-Windows 7 codebase. Another one is to rework it to make it more obvious.
claunia added the Issue-FeatureProduct-ConhostArea-UserInterface labels 2026-01-31 07:14:02 +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 Area-UserInterface Issue-Feature Product-Conhost
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#20444
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?