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

Cascadia Code not the new default in 0.5 like it's supposed to be #4056

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

Originally created by @cprivitere on GitHub (Sep 25, 2019).

Environment

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

If it matters, Cascadia Code was already installed on this machine before the update.

Steps to reproduce

Update to the new Terminal 0.5.2661.0.
Delete all content from profiles.json.
Relaunch Terminal and let it regenerate defaults.
Hold down Alt while clicking Settings to see the defaults.
Scroll down and see that Consolas is still being used as the default.
New size actually is 12, btw.

Expected behavior

Should be using Cascadia Code as per the release notes.

Actual behavior

Is still using Consolas.

Originally created by @cprivitere on GitHub (Sep 25, 2019). # Environment ```none Windows build number: Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): 0.5.2661.0 If it matters, Cascadia Code was already installed on this machine before the update. ``` # Steps to reproduce Update to the new Terminal 0.5.2661.0. Delete all content from profiles.json. Relaunch Terminal and let it regenerate defaults. Hold down Alt while clicking Settings to see the defaults. Scroll down and see that Consolas is still being used as the default. New size actually is 12, btw. # Expected behavior Should be using Cascadia Code as per the release notes. # Actual behavior Is still using Consolas.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:36:59 +00:00
claunia commented 2026-01-30 23:36:59 +00:00
Author
Owner
Copy Link

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

The release notes indicate that it’s included, not that it’s the default. We didn’t think it had broad enough character range coverage to be made the default font.

@DHowett-MSFT commented on GitHub (Sep 25, 2019): The release notes indicate that it’s _included_, not that it’s the default. We didn’t think it had broad enough character range coverage to be made the default font.
claunia commented 2026-01-30 23:37:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 25, 2019):

I don't believe the release notes say anything about us using Cascadia Code as the new font by default 😜 . We're simply shipping the font with the terminal for now. If you want to set it as your font, feel free to, but until we work out some additional bugs in the font, we didn't feel comfortable shipping it as the default font for everyone.

@zadjii-msft commented on GitHub (Sep 25, 2019): I don't believe the release notes say anything about us using Cascadia Code as the new font by default 😜 . We're simply shipping the font _with_ the terminal for now. If you want to set it as your font, feel free to, but until we work out some additional bugs in the font, we didn't feel comfortable shipping it as the default font for everyone.
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#4056
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?