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

Rethink settings grouping #2059

New Issue
Closed
opened 2026-01-30 22:45:45 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:45:45 +00:00
Owner
Copy Link

Originally created by @mcpiroman on GitHub (Jun 24, 2019).

Referencing #754 and #1448, I think it's best to abandon separation between global/profile settings. Instead each setting could go to anywhere, but with profile settings overwriting global ones. There still will need to be global-only settings like showTabsInTitlebar or defaultProfile, but others could be made available as per-profile (e.g. keybindings or initialCols).

Additionally, I suggest a 'property groups' - groups of settings that you can '#include' in profiles (like include: ["guid1", "guid2"]). E.g. you may want to have consistent settings between wsl distros and anothers between cmd/ps profiles. (I can easily imagine profiles that differ only in command line, starting path or something like this, but have other settings, mostly, shared.)

Issues:

  • How should default settings look (what goes where?)
  • Design of settings GUI that support this might be hard
Originally created by @mcpiroman on GitHub (Jun 24, 2019). Referencing #754 and #1448, I think it's best to abandon separation between global/profile settings. Instead each setting could go to anywhere, but with profile settings overwriting global ones. There still will need to be global-only settings like `showTabsInTitlebar` or `defaultProfile`, but others could be made available as per-profile (e.g. `keybindings` or `initialCols`). Additionally, I suggest a 'property groups' - groups of settings that you can '`#include`' in profiles (like `include: ["guid1", "guid2"]`). E.g. you may want to have consistent settings between wsl distros and anothers between cmd/ps profiles. (I can easily imagine profiles that differ only in command line, starting path or something like this, but have other settings, mostly, shared.) Issues: - How should default settings look (what goes where?) - Design of settings GUI that support this might be hard
claunia added the Issue-FeatureArea-SettingsResolution-DuplicateProduct-Terminal labels 2026-01-30 22:45:45 +00:00
claunia commented 2026-01-30 22:45:47 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

This'll probably be helped out a lot by #754 -- i'd like to hold off on further settings discussions until that one lands. We'd be happy to hear your settings feedback in 754 or on the spec review #1258.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): This'll probably be helped out a lot by #754 -- i'd like to hold off on further settings discussions until that one lands. We'd be happy to hear your settings feedback in 754 or on the spec review #1258.
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 Issue-Feature Product-Terminal Resolution-Duplicate
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#2059
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?