microsoft / microsoft/terminal
Cannot override Cascadia Code
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
Environment
Win32NT 10.0.18362.0
Windows Terminal version: 0.5.2681.0
Steps to reproduce
Download the latest install of Windows Terminal from the Microsoft Store.
Install a new version of Cascadia Code (attached) via the font menu.
Open Windows Terminal.
Set Font Family in Preferences to “Cascadia Code”.
Observe that glyphs present in the older version appear (it appears that the newer font is used as a fallback for the previously-missing glyphs).
Expected behavior
Windows Terminal should use a normal process to install Cascadia Code so that it can be uninstalled or replaced as new versions of Cascadia Code are released.
Actual behavior
Note here that the older version of the font is being used for glyphs present in the older version, but the newer font is being used for glyphs only present in the newer version.
Windows Terminal appears to have a ‘back-end’ way of installing the font file that is inaccessible and cannot be overriden even when installing through the Font Menu, or a Font manager (such as FEX).
In VS Code, the newer version of the font is ignore entirely in favor of the older version installed by Windows Terminal.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.