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

Terminal defaults to powershell ignoring settings #7710

New Issue
Closed
opened 2026-01-31 01:10:56 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:10:56 +00:00
Owner
Copy Link

Originally created by @simmessa on GitHub (Apr 26, 2020).

Environment

Win32NT             10.0.19592.0 Microsoft Windows NT 10.0.19592.0
Windows Terminal version (if applicable):
Version: 0.11.1121.0

Steps to reproduce

Just open Windows Terminal, and the starting shell is powershell, regardless of "defaultProfile" setting in global (settings.json).

I don't really know of any other things that might trigger this.

Expected behavior

Windows Terminal should just honor my settings and open Ubuntu as default profile (the guid is specified in defaultProfile).

Actual behavior

A powershell prompt is started

image

Originally created by @simmessa on GitHub (Apr 26, 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. --> # Environment ```none Win32NT 10.0.19592.0 Microsoft Windows NT 10.0.19592.0 Windows Terminal version (if applicable): Version: 0.11.1121.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Just open Windows Terminal, and the starting shell is powershell, regardless of "defaultProfile" setting in global (settings.json). I don't really know of any other things that might trigger this. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows Terminal should just honor my settings and open Ubuntu as default profile (the guid is specified in defaultProfile). # Actual behavior <!-- What's actually happening? --> A powershell prompt is started ![image](https://user-images.githubusercontent.com/1277216/80307419-47bd8380-87c9-11ea-8d04-9f8850d1d1f0.png)
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 01:10:56 +00:00
claunia commented 2026-01-31 01:10:57 +00:00
Author
Owner
Copy Link

@simmessa commented on GitHub (Apr 26, 2020):

Ok, I just had a look at the release notes and realized it's supposed to work this way...

https://github.com/microsoft/terminal/releases

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.
Failure to do so will cause us to ignore your default profile, launch mode, etc., etc.

But let me say, since pretty much all of us have this on autoupdate from the Windows store, this very far from the best user experience, especially for people who have been part of the alpha since the beginning (yours truly).

Suddenly the app updates, you might not even realize it and... boom, part of your settings aren't used anymore and you head to github to file for a nasty bug...

I'd suggest doing SOMETHING to notify users of this BREAKING change, otherwise this makes me feel pretty stupid...

For example? Open a window on the first launch showing the DAMN release notes... that might be a nice approach IMHO. It's very similar to what's used in... let me think of a modern example... uhm have you heard about the little app called VsCode ?

Sorry for the sarcasm, I love your work and would love even more if you paid more attention to this kind of things.

Thank you for your time and patience.

S.

@simmessa commented on GitHub (Apr 26, 2020): Ok, I just had a look at the release notes and realized it's supposed to work this way... https://github.com/microsoft/terminal/releases ``` 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. Failure to do so will cause us to ignore your default profile, launch mode, etc., etc. ``` But let me say, since pretty much all of us have this on autoupdate from the Windows store, this very far from the best user experience, especially for people who have been part of the alpha since the beginning (yours truly). Suddenly the app updates, you might not even realize it and... boom, part of your settings aren't used anymore and you head to github to file for a nasty bug... I'd suggest doing SOMETHING to notify users of this **BREAKING** change, otherwise this makes me feel pretty stupid... For example? Open a window on the first launch showing the DAMN release notes... that might be a nice approach IMHO. It's very similar to what's used in... let me think of a modern example... uhm have you heard about the little app called _VsCode_ ? Sorry for the sarcasm, I love your work and would love even more if you paid more attention to this kind of things. Thank you for your time and patience. S.
claunia commented 2026-01-31 01:10:57 +00:00
Author
Owner
Copy Link

@simmessa commented on GitHub (Apr 26, 2020):

Hopefully this non-existent issue can help other ppl by pointing to the release notes:

https://github.com/microsoft/terminal/releases/tag/v0.11.1121.0

The Problem

“Globals” namespace
The Terminal no longer supports the globals property in the JSON file. If you have settings inside the globals object, they will be ignored. To fix this, remove the globals object and move your global settings into the root of the JSON file.

more infos here:
https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release/

image

The Fix

Discard globals and move them to the json root:

image

After that it's good. Have fun!

@simmessa commented on GitHub (Apr 26, 2020): Hopefully this non-existent issue can help other ppl by pointing to the release notes: https://github.com/microsoft/terminal/releases/tag/v0.11.1121.0 ## The Problem ``` “Globals” namespace The Terminal no longer supports the globals property in the JSON file. If you have settings inside the globals object, they will be ignored. To fix this, remove the globals object and move your global settings into the root of the JSON file. ``` more infos here: https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release/ ![image](https://user-images.githubusercontent.com/1277216/80307687-e1d1fb80-87ca-11ea-8662-0fe05bf3cf8f.png) ## The Fix Discard globals and move them to the json root: ![image](https://user-images.githubusercontent.com/1277216/80307715-22317980-87cb-11ea-9fd7-e4aeca23cfde.png) After that it's good. Have fun!
claunia commented 2026-01-31 01:10:57 +00:00
Author
Owner
Copy Link

@MortalAndTry commented on GitHub (Apr 27, 2020):

good job. Solved my problem.

@MortalAndTry commented on GitHub (Apr 27, 2020): good job. Solved my problem.
claunia commented 2026-01-31 01:10:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 27, 2020):

Hey @simmessa

especially for people who have been part of the alpha since the beginning (yours truly).

Thanks for being with us so long. I appreciate that this has been a terrible obnoxious and sudden change for everyone, and I’m really sorry about the communication—or lack thereof—here. One of the things that we’re hoping to roll out after we launch 1.0 is some sort of update notification with release notes (#5513, colorfully-titled by our community). We ended up batching all the breaking changes up until the end of the preview cycle, but I’d like to assure you that post-v1 settings changes will be accompanied with migrators, notifications or just good old-fashioned backwards compatibility.

@DHowett-MSFT commented on GitHub (Apr 27, 2020): Hey @simmessa > especially for people who have been part of the alpha since the beginning (yours truly). Thanks for being with us so long. I appreciate that this has been a terrible obnoxious and sudden change for everyone, and I’m really sorry about the communication—or lack thereof—here. One of the things that we’re hoping to roll out after we launch 1.0 is some sort of update notification with release notes (#5513, colorfully-titled by our community). We ended up batching all the breaking changes up until the end of the preview cycle, but I’d like to assure you that post-v1 settings changes will be accompanied with migrators, notifications or just good old-fashioned backwards compatibility.
claunia commented 2026-01-31 01:10:58 +00:00
Author
Owner
Copy Link

@simmessa commented on GitHub (Apr 27, 2020):

Hi Dustin,

sure, no problem, please forgive my rant, it's nice to know you're working on #5513. That kind of functionality will surely make things much smoother for all of us!

Again, you've done some outstanding job and now that V1 is here I can't wait to put my CLI hands on it :)

@simmessa commented on GitHub (Apr 27, 2020): Hi Dustin, sure, no problem, please forgive my rant, it's nice to know you're working on #5513. That kind of functionality will surely make things much smoother for all of us! Again, you've done some outstanding job and now that V1 is here I can't wait to put my CLI hands on it :)
claunia commented 2026-01-31 01:10:58 +00:00
Author
Owner
Copy Link

@kapcod commented on GitHub (Apr 27, 2020):

@simmessa I think that, in addition to showing the message, they could have just migrated it automatically

@kapcod commented on GitHub (Apr 27, 2020): @simmessa I think that, in addition to showing the message, they could have just migrated it automatically
claunia commented 2026-01-31 01:10:58 +00:00
Author
Owner
Copy Link

@simmessa commented on GitHub (Apr 27, 2020):

@crazyshot yes that would have been ideal but...guess they also had a lot of better /more useful things to do :D

@simmessa commented on GitHub (Apr 27, 2020): @crazyshot yes that would have been ideal but...guess they also had a lot of better /more useful things to do :D
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#7710
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?