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

Some default profiles have a different effective default for useAcrylic than the JSON schema #4073

New Issue
Closed
opened 2026-01-30 23:37:18 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:37:18 +00:00
Owner
Copy Link

Originally created by @heaths on GitHub (Sep 26, 2019).

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2681.0

Any other software? Applicable to this issue, no.

Steps to reproduce

  1. Install Terminal (Preview) from Microsoft Store.
  2. Start each of the default shells.

Expected behavior

All shells default to effectively ```"useAcrylic": false`.

Actual behavior

It varies. Windows PowerShell and PowerShell Core default to no acrylic. Cmd, Ubuntu, and Azure Cloud Shell default to use acrylic. If you edit settings and type "useAcrylic" for a profile, VSCode (or, I imagine, any software that supports JSON schema) adds "useAcrylic": false. If the default setting is false, then why do some profiles use it by default?

Originally created by @heaths on GitHub (Sep 26, 2019). # Environment ```none Windows build number: Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): 0.5.2681.0 Any other software? Applicable to this issue, no. ``` # Steps to reproduce 1. Install Terminal (Preview) from Microsoft Store. 2. Start each of the default shells. # Expected behavior All shells default to effectively ```"useAcrylic": false`. # Actual behavior It varies. Windows PowerShell and PowerShell Core default to no acrylic. Cmd, Ubuntu, and Azure Cloud Shell default to use acrylic. If you edit settings and type "useAcrylic" for a profile, VSCode (or, I imagine, any software that supports JSON schema) adds `"useAcrylic": false`. If the default setting is false, then why do some profiles use it by default?
claunia added the Resolution-By-DesignNeeds-Tag-Fix labels 2026-01-30 23:37:18 +00:00
claunia commented 2026-01-30 23:37:19 +00:00
Author
Owner
Copy Link

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

The default in the schema isn’t exactly a default, I learned: its more of a “what will a complying text editor automatically insert for you” (when talking about autogeneration of values). The default profiles are configured to provide a little bit of flair so users know what to expect from their options.

@DHowett-MSFT commented on GitHub (Sep 26, 2019): The default in the schema isn’t exactly a _default_, I learned: its more of a “what will a complying text editor automatically insert for you” (when talking about autogeneration of values). The default profiles are configured to provide a little bit of flair so users know what to expect from their options.
claunia commented 2026-01-30 23:37:19 +00:00
Author
Owner
Copy Link

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

(just had a chat with the team: They agree with this assertion. I'm going to close this out.)

@DHowett-MSFT commented on GitHub (Sep 26, 2019): (just had a chat with the team: They agree with this assertion. I'm going to close this out.)
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 Resolution-By-Design
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#4073
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?