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

MEGATHREAD: Breaking settings changes in version 0.11! #7532

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

Originally created by @DHowett-MSFT on GitHub (Apr 22, 2020).

BREAKING SETTINGS CHANGES IN 0.11

  • BREAKING CHANGE We've deleted a lot of legacy settings handling (#5190)
    • Please see our blog post and our most recent status update for more information.
    • If you had settings hanging out in the globals dictionary, you'll want to move them out.
      • REMEDIATION: move everything from globals to the root of your settings file and delete the empty globals object.
      • Failure to do so will cause us to ignore your default profile, launch mode, etc., etc.
      • THIS INCLUDES defaultProfile
    • requestedTheme has been renamed to theme (#5265)
  • profiles.json has been renamed to settings.json. This should be transparent to you as we'll rename it on first launch (#5199)
    • As a side effect, we'll finally stop resurrecting old pre-version-0.3 roaming profiles.
  • If you don't specify a splitPane split mode, it'll default to automatic (#5194)
  • copy's original and poorly-understood trimWhitespace argument is now called singleLine to indicate that it will, in fact, copy text as a single line (#5216)
  • The default font for any profiles that don't specify a font is now Cascadia Mono (#5121)

Do your settings look like this?

{
    "globals": {
        "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
        "initialCols": 200,
        "initialRows": 65,
        "initialPosition": "0,0",
        "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502",
        "confirmCloseAllTabs": true,
        "keybindings": [
            ...
        ]
    },
    "profiles": {
        ...
    }
}

Then change them to look like this:

{
    "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
    "initialCols": 200,
    "initialRows": 65,
    "initialPosition": "0,0",
    "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502",
    "confirmCloseAllTabs": true,
    "keybindings": [
        ...
    ],
    "profiles": {
        ...
    }
}

Or even better, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.

Originally created by @DHowett-MSFT on GitHub (Apr 22, 2020). # BREAKING SETTINGS CHANGES IN 0.11 * **BREAKING CHANGE** We've deleted a lot of legacy settings handling (#5190) * Please see [our blog post](https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release) and [our most recent status update](https://github.com/microsoft/terminal/issues/3600#issuecomment-608654738) for more information. * If you had settings hanging out in the `globals` dictionary, you'll want to move them out. * **REMEDIATION**: move everything from `globals` to the root of your settings file and delete the empty `globals` object. * Failure to do so will cause us to ignore your default profile, launch mode, etc., etc. * **THIS INCLUDES `defaultProfile`** * `requestedTheme` has been renamed to `theme` (#5265) * `profiles.json` has been renamed to `settings.json`. This should be transparent to you as we'll rename it on first launch (#5199) * As a side effect, we'll finally stop resurrecting _old_ pre-version-0.3 roaming profiles. * If you don't specify a `splitPane` `split` mode, it'll default to `automatic` (#5194) * `copy`'s original and poorly-understood `trimWhitespace` argument is now called `singleLine` to indicate that it will, in fact, copy text _as a single line_ (#5216) * The default font for any profiles that don't specify a font is now _[Cascadia Mono](https://github.com/microsoft/cascadia-code)_ (#5121) <hr> Do your settings look like this? ```json { "globals": { "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "initialCols": 200, "initialRows": 65, "initialPosition": "0,0", "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502", "confirmCloseAllTabs": true, "keybindings": [ ... ] }, "profiles": { ... } } ``` Then change them to look like this: ```json { "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "initialCols": 200, "initialRows": 65, "initialPosition": "0,0", "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502", "confirmCloseAllTabs": true, "keybindings": [ ... ], "profiles": { ... } } ``` Or **even better**, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.
claunia added the Issue-QuestionArea-SettingsNeeds-Tag-FixProduct-Terminal labels 2026-01-31 01:06:21 +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-Question Needs-Tag-Fix 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#7532
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?