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

defaultProfile setting is no longer respected #7575

New Issue
Closed
opened 2026-01-31 01:07:37 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:07:37 +00:00
Owner
Copy Link

Originally created by @zawor on GitHub (Apr 23, 2020).

It seems like after upgrading to 0.11.1121.0 defaultProfile setting is no longer respected.

Environment

Windows build number: Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 0.11.1121.0

Any other software?
plenty but probably irrelevant ;)

Steps to reproduce

  1. Have a multiple profiles configured where powershell.exe is not default.
  2. Start Windows terminal
  3. You start always with powershell.exe one

alternatively
2. ctrl +alt + - causes always to load powershell.exe one regardless which one currently is active

Expected behavior

defaultProfile gets loaded on startup

Actual behavior

defaultProfile is ignored

I attach settings file for reference:
settings.zip

PS:
If you need more details simply let me know.

Originally created by @zawor on GitHub (Apr 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> It seems like after upgrading to 0.11.1121.0 `defaultProfile` setting is no longer respected. # Environment ```none Windows build number: Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): 0.11.1121.0 Any other software? plenty but probably irrelevant ;) ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Have a multiple profiles configured where `powershell.exe` is not default. 2. Start Windows terminal 3. You start always with `powershell.exe` one alternatively 2. `ctrl` +`alt` + `-` causes always to load `powershell.exe` one regardless which one currently is active # Expected behavior `defaultProfile` gets loaded on startup # Actual behavior `defaultProfile` is ignored I attach settings file for reference: [settings.zip](https://github.com/microsoft/terminal/files/4520837/settings.zip) PS: If you need more details simply let me know.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 01:07:37 +00:00
claunia commented 2026-01-31 01:07:38 +00:00
Author
Owner
Copy Link

@mlewand commented on GitHub (Apr 23, 2020):

You need to move all your settings from global key (in your settings.json) outside of global key (to the root level).

Duplicate of #5458.

@mlewand commented on GitHub (Apr 23, 2020): You need to move all your settings from `global` key (in your `settings.json`) outside of `global` key (to the root level). Duplicate of #5458.
claunia commented 2026-01-31 01:07:38 +00:00
Author
Owner
Copy Link

@zawor commented on GitHub (Apr 23, 2020):

this solves my problem... but damn... visibility of this breaking change is close to none if you are not tracking terminal changes eagerly...

Anyway thank you for resolving my issue! :)

@zawor commented on GitHub (Apr 23, 2020): this solves my problem... but damn... visibility of this breaking change is close to none if you are not tracking terminal changes eagerly... Anyway thank you for resolving my issue! :)
claunia commented 2026-01-31 01:07:38 +00:00
Author
Owner
Copy Link

@mlewand commented on GitHub (Apr 23, 2020):

@zawor agree, I also missed it myself, despite "reading" (or scanning, I should say) the changelog (https://github.com/microsoft/terminal/issues/5458#issuecomment-618243148) 😄

@mlewand commented on GitHub (Apr 23, 2020): @zawor agree, I also missed it myself, despite "reading" (or scanning, I should say) the changelog (https://github.com/microsoft/terminal/issues/5458#issuecomment-618243148) :smile:
claunia commented 2026-01-31 01:07:38 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Apr 23, 2020):

I was trying to update my settings to set the theme, and I was trying to put the entry in the defaults section, wondering why it wasn't working - until I moved it to root.

It feels quite odd using the JSON root for elements, but I guess once the Settings UI is added, it will become redundant to think too much about it. :)

@mdtauk commented on GitHub (Apr 23, 2020): I was trying to update my settings to set the theme, and I was trying to put the entry in the defaults section, wondering why it wasn't working - until I moved it to root. It feels quite odd using the JSON root for elements, but I guess once the Settings UI is added, it will become redundant to think too much about it. :)
claunia commented 2026-01-31 01:07:38 +00:00
Author
Owner
Copy Link

@zawor commented on GitHub (Apr 23, 2020):

@mlewand mine was even worse... i run on windows store version, so today out of sudden i got caught with my pants down by this regression :P

personally i would love to have (opt in) possibility to get smacked in the face with release notes dialog/tab/view/whatever every time i get auto updated, lets say just like in VS Code

@zawor commented on GitHub (Apr 23, 2020): @mlewand mine was even worse... i run on windows store version, so today out of sudden i got caught with my pants down by this regression :P personally i would love to have (opt in) possibility to get smacked in the face with release notes dialog/tab/view/whatever every time i get auto updated, lets say just like in VS Code
claunia commented 2026-01-31 01:07:39 +00:00
Author
Owner
Copy Link

@mlewand commented on GitHub (Apr 23, 2020):

@zawor Sounds like a good feature request 🙂 what I'm doing is I subscribed to release-only on GH so that I get notification about the release, check the changelog and then upgrade it using chocolatey (decent package manager, so the upgrade is as simple as typing cup microsoft-windows-terminal /y once I'm sure I want to upgrade).

@mlewand commented on GitHub (Apr 23, 2020): @zawor Sounds like a good feature request 🙂 what I'm doing is I subscribed to release-only on GH so that I get notification about the release, check the changelog and then upgrade it using [chocolatey](https://chocolatey.org/) (decent package manager, so the upgrade is as simple as typing `cup microsoft-windows-terminal /y` once I'm sure I want to upgrade).
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 Needs-Tag-Fix Needs-Triage
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#7575
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?