starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Stop roaming settings for now #2475

New Issue
Open
opened 2026-01-30 22:55:59 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:55:59 +00:00
Owner
Copy Link

Originally created by @DHowett-MSFT on GitHub (Jul 2, 2019).

Originally assigned to: @zadjii-msft on GitHub.

Until we come up with a good story for settings overrides and default profiles on different machines, we're going to want to move the settings from RoamingState to LocalState. Since right now a user's settings include everything we know about them for a specific machine, we're not capable of safely roaming them.

Roaming machine-specific settings causes (but is not limited to causing) the following issues:

  • instant exit on launch because default shell has gone away
  • new install's settings stomping other machines
  • spurious changes at runtime resulting in syncs from other machines, changing settings unexpectedly

We should make the move to localstate sooner rather than later, since we only just released v0.2. This is still going to be a minor breaking change, but we should include some migration logic.

That migration logic should use a file move (instead of a read-parse-write cycle), as some folks are using symbolic links to manage their settings.

Refer:

Originally created by @DHowett-MSFT on GitHub (Jul 2, 2019). Originally assigned to: @zadjii-msft on GitHub. Until we come up with a good story for settings overrides and default profiles on different machines, we're going to want to move the settings from `RoamingState` to `LocalState`. Since right now a user's settings include everything we know about them _for a specific machine_, we're not capable of safely roaming them. Roaming machine-specific settings causes (but is not limited to causing) the following issues: * instant exit on launch because default shell has gone away * new install's settings stomping other machines * spurious changes at runtime resulting in syncs from other machines, changing settings unexpectedly We should make the move to localstate sooner rather than later, since we only just released v0.2. This is still going to be a minor breaking change, but we should include some migration logic. That migration logic **should** use a file move (instead of a read-parse-write cycle), as some folks are using symbolic links to manage their settings. Refer: * #1567 * #1455 * #1399 * #1654
claunia added the Resolution-Fix-CommittedArea-SettingsIssue-TaskProduct-Terminal labels 2026-01-30 22:55:59 +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-Settings Issue-Task Product-Terminal Resolution-Fix-Committed
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#2475
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?