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

Profile default settings not supported even though valid against schema #5700

New Issue
Closed
opened 2026-01-31 00:19:27 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:19:27 +00:00
Owner
Copy Link

Originally created by @brunovieira97 on GitHub (Dec 26, 2019).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.7.3451.0

Steps to reproduce

  1. Open profiles.json
  2. Change profile settings so it has the following structure:
"profiles": {
	"defaults": {
		"acrylicOpacity": 0.95,
		"colorScheme": "Campbell",
		"cursorColor": "#FFFFFF",
		"fontFace": "Cascadia Code PL",
		"fontSize": 11,
		"historySize": 9001,
		"padding": "5, 0, 0, 0",
		"useAcrylic": true
	},
	"list": [
		{
			"name": "Windows PowerShell",
			"guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
			"commandline": "powershell.exe"
		},
		{
			"name": "cmd",
			"guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
			"commandline": "cmd.exe"
		}
}
  1. Restart the Windows Terminal

Expected behavior

Windows Terminal starts and applies the settings correctly, using the ones in "defaults" for every profile and the ones in each item of "list" for the specific profile.

Actual behavior

Windows Terminal shows an error dialog with the following message:

Settings could not be loaded from file. Check for syntax errors, including trailing commas.

Temporarily using the Windows Terminal default settings.

I checked the profiles.json schema and it seems to be correct, even though Terminal app doesn't parse/identify them correctly. There's this "variable" on my profiles file:

"$schema": "https://aka.ms/terminal-profiles-schema"

Already checked for trailing commas and any syntax errors, everything seems correct. Also, I did comment out the defaults and list tags, reverting the profiles.json to an array, therefore having duplicated settings on each profile (like it used to be on first releases) and it works fine then.

Originally created by @brunovieira97 on GitHub (Dec 26, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.7.3451.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open profiles.json 2. Change profile settings so it has the following structure: ``` "profiles": { "defaults": { "acrylicOpacity": 0.95, "colorScheme": "Campbell", "cursorColor": "#FFFFFF", "fontFace": "Cascadia Code PL", "fontSize": 11, "historySize": 9001, "padding": "5, 0, 0, 0", "useAcrylic": true }, "list": [ { "name": "Windows PowerShell", "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "commandline": "powershell.exe" }, { "name": "cmd", "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "commandline": "cmd.exe" } } ``` 3. Restart the Windows Terminal # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows Terminal starts and applies the settings correctly, using the ones in "defaults" for every profile and the ones in each item of "list" for the specific profile. # Actual behavior <!-- What's actually happening? --> Windows Terminal shows an error dialog with the following message: ``` Settings could not be loaded from file. Check for syntax errors, including trailing commas. Temporarily using the Windows Terminal default settings. ``` I checked the `profiles.json` schema and it seems to be correct, even though Terminal app doesn't parse/identify them correctly. There's this "variable" on my profiles file: ``` "$schema": "https://aka.ms/terminal-profiles-schema" ``` Already checked for trailing commas and any syntax errors, everything seems correct. Also, I did comment out the `defaults` and `list` tags, reverting the `profiles.json` to an array, therefore having duplicated settings on each profile (like it used to be on first releases) and it works fine then.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 00:19:27 +00:00
claunia commented 2026-01-31 00:19:28 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 26, 2019):

This schema update was made in anticipation of the upcoming 0.8 release. It’s fair feedback, however, that our schema tracking master will prove to be somewhat annoying until we stop adding new features.

@DHowett-MSFT commented on GitHub (Dec 26, 2019): This schema update was made in anticipation of the upcoming 0.8 release. It’s fair feedback, however, that our schema tracking master will prove to be somewhat annoying until we stop adding new features.
claunia commented 2026-01-31 00:19:28 +00:00
Author
Owner
Copy Link

@ChristoferK commented on GitHub (Jan 5, 2020):

@brunovieira97, your "list" array doesn't have a closing ].

@ChristoferK commented on GitHub (Jan 5, 2020): @brunovieira97, your `"list"` array doesn't have a closing `]`.
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#5700
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?