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

warning popup "Cascadia Mono font is not found" (unpackaged version) #20833

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

Originally created by @g-chauvel on GitHub (Nov 16, 2023).

Windows Terminal version

1.18.3181.0 (unpackaged 1.18.231114001)

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

It looks like the bug fix for "The regression where "Cascadia Mono" (or "... Code") would not be found on upgrade has been un-regressed (https://github.com/microsoft/terminal/pull/16196)" introduced a regression for the unpackaged version

Launch WindowsTerminal.exe from unpackaged version

Expected Behavior

  • no warning popup from WindowsTerminal.exe unpackaged version 1.18.3181.0 (unpackaged 1.18.231114001)
  • no warning popup from WindowsTerminal.exe unpackaged version 1.18.2822.0 (unpackaged 1.18.231009002-preview)

Actual Behavior

  • a warning popup: "Cascadia Mono font is not found, Consolas is used instead" from WindowsTerminal.exe unpackaged version 1.18.3181.0 (unpackaged 1.18.231114001) is displayed
  • no warning popup from WindowsTerminal.exe unpackaged version 1.18.2822.0 (unpackaged 1.18.231009002-preview)

with the same default profile from C:...\AppData\Local\Microsoft\Windows Terminal\settings.json settings

{
    "altGrAliasing": true,
    "antialiasingMode": "grayscale",
    "closeOnExit": "automatic",
    "colorScheme": "Campbell",
    "commandline": "C:\\...\\PowerShell-7.3\\pwsh.exe",
    "cursorShape": "bar",
    "font":
    {
        "face": "Cascadia Mono",
        "size": 10.0
    },
    "guid": "....",
    "hidden": false,
    "historySize": 9001,
    "icon": "C:\\...\\PowerShell-7.3\\assets\\Square44x44Logo.png",
    "name": "Pwsh 7.3",
    "padding": "8, 8, 8, 8",
    "snapOnInput": true,
    "startingDirectory": "%USERPROFILE%",
    "useAcrylic": false
},
Originally created by @g-chauvel on GitHub (Nov 16, 2023). ### Windows Terminal version 1.18.3181.0 (unpackaged 1.18.231114001) ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce It looks like the bug fix for "The regression where "Cascadia Mono" (or "... Code") would not be found on upgrade has been un-regressed (https://github.com/microsoft/terminal/pull/16196)" introduced a regression for the unpackaged version Launch WindowsTerminal.exe from unpackaged version - https://github.com/microsoft/terminal/releases/download/v1.18.3181.0/Microsoft.WindowsTerminal_1.18.3181.0_x64.zip - https://github.com/microsoft/terminal/releases/download/v1.18.2822.0/Microsoft.WindowsTerminal_1.18.2822.0_x64.zip ### Expected Behavior - no warning popup from WindowsTerminal.exe unpackaged version 1.18.3181.0 (unpackaged 1.18.231114001) - no warning popup from WindowsTerminal.exe unpackaged version 1.18.2822.0 (unpackaged 1.18.231009002-preview) ### Actual Behavior - a warning popup: "Cascadia Mono font is not found, Consolas is used instead" from WindowsTerminal.exe unpackaged version 1.18.3181.0 (unpackaged 1.18.231114001) is displayed - no warning popup from WindowsTerminal.exe unpackaged version 1.18.2822.0 (unpackaged 1.18.231009002-preview) with the same default profile from C:\...\AppData\Local\Microsoft\Windows Terminal\settings.json settings ```json { "altGrAliasing": true, "antialiasingMode": "grayscale", "closeOnExit": "automatic", "colorScheme": "Campbell", "commandline": "C:\\...\\PowerShell-7.3\\pwsh.exe", "cursorShape": "bar", "font": { "face": "Cascadia Mono", "size": 10.0 }, "guid": "....", "hidden": false, "historySize": 9001, "icon": "C:\\...\\PowerShell-7.3\\assets\\Square44x44Logo.png", "name": "Pwsh 7.3", "padding": "8, 8, 8, 8", "snapOnInput": true, "startingDirectory": "%USERPROFILE%", "useAcrylic": false },
claunia added the Needs-TriageIssue-BugIn-PR labels 2026-01-31 07:25:22 +00:00
claunia commented 2026-01-31 07:25:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 16, 2023):

@lhecker did we somehow break this for unpackaged in #16196

@zadjii-msft commented on GitHub (Nov 16, 2023): @lhecker did we somehow break this for unpackaged in #16196
claunia commented 2026-01-31 07:25:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 16, 2023):

Yes. 🤦 You see, because DxEngine modifies the only copy of the chosen face name to do a variant search (i.e. "Arial Bold" -> "Arial", if the former doesn't exist). So by moving the nearby search after the variant search, I broke the lookup because now it searches for "Cascadia".

FYI the code for "AtlasEngine" works correctly. You can enable it in the "Rendering" settings and enable it, as it'll be the default in the near term anyways.

@lhecker commented on GitHub (Nov 16, 2023): Yes. 🤦 You see, because DxEngine modifies the *only* copy of the chosen face name to do a variant search (i.e. "Arial Bold" -> "Arial", if the former doesn't exist). So by moving the nearby search after the variant search, I broke the lookup because now it searches for "Cascadia". FYI the code for "AtlasEngine" works correctly. You can enable it in the "Rendering" settings and enable it, as it'll be the default in the near term anyways.
claunia commented 2026-01-31 07:25:24 +00:00
Author
Owner
Copy Link

@g-chauvel commented on GitHub (Nov 16, 2023):

FYI the code for "AtlasEngine" works correctly. You can enable it in the "Rendering" settings and enable it, as it'll be the default in the near term anyways.

AtlasEngine enabled, no more warning popup

@g-chauvel commented on GitHub (Nov 16, 2023): > FYI the code for "AtlasEngine" works correctly. You can enable it in the "Rendering" settings and enable it, as it'll be the default in the near term anyways. AtlasEngine enabled, no more warning popup
claunia commented 2026-01-31 07:25:24 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Nov 16, 2023):

The same problem if font installed in user's font directory. If font installed globally there is no issue.

@237dmitry commented on GitHub (Nov 16, 2023): The same problem if font installed in user's font directory. If font installed globally there is no issue.
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 In-PR Issue-Bug 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#20833
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?