Do not bundle Cascadia Code #15879

Closed
opened 2026-01-31 04:51:10 +00:00 by claunia · 3 comments
Owner

Originally created by @SharakPL on GitHub (Nov 13, 2021).

Description of the new feature/enhancement

I have a hard time managing Cascadia Code on Windows 10. I install all new fonts with Scoop eg. scoop install Cascadia-Code and I keep it up to date. I've installed v.2110.31 almost 2 weeks ago when it was released, but now I see I have only powerline (Code PL and Mono PL) versions updated. Somehow Code and Mono remained at v.2108. I thought it's maybe because I updated Terminal recently which is bundled with this older versions and doesn't include PL variants so I reinstalled whole package through Scoop but the effect is still the same - only PL are new. Looks like the Windows Terminal is blocking font update.

Updated whole package (CC, CC PL, CM, CM PL):

obraz

Terminal font doesn't udpate:

obraz

Proposed technical implementation details (optional)

Let users handle font installation or at least make it installed in default way so it could be updated anytime by the admin and not only by Windows Terminal update.

Originally created by @SharakPL on GitHub (Nov 13, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement I have a hard time managing Cascadia Code on Windows 10. I install all new fonts with [Scoop](https://scoop.sh/) eg. `scoop install Cascadia-Code` and I keep it up to date. I've installed v.2110.31 almost 2 weeks ago when it was released, but now I see I have only powerline (Code PL and Mono PL) versions updated. Somehow Code and Mono remained at v.2108. I thought it's maybe because I updated Terminal recently which is bundled with this older versions and doesn't include PL variants so I reinstalled whole package through Scoop but the effect is still the same - only PL are new. Looks like the Windows Terminal is blocking font update. ### Updated whole package (CC, CC PL, CM, CM PL): ![obraz](https://user-images.githubusercontent.com/5007456/141661986-847f1045-f027-4ed1-acd6-8c3267ea0bec.png) ### Terminal font doesn't udpate: ![obraz](https://user-images.githubusercontent.com/5007456/141661969-8d67af67-a641-4148-98e7-0e79a4e25e4c.png) <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Let users handle font installation or at least make it installed in default way so it could be updated anytime by the admin and not only by Windows Terminal update. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:51:10 +00:00
Author
Owner

@j4james commented on GitHub (Nov 14, 2021):

I think this may be the same problem described in issue #2979.

@j4james commented on GitHub (Nov 14, 2021): I think this may be the same problem described in issue #2979.
Author
Owner

@zadjii-msft commented on GitHub (Nov 15, 2021):

Yea, this is basically /dup #2979. I believe we're actually going to do something about this very soon, so I'm gonna go move that one up to 1.13. Thanks!

@zadjii-msft commented on GitHub (Nov 15, 2021): Yea, this is basically /dup #2979. I believe we're actually going to do something about this _very_ soon, so I'm gonna go move that one up to 1.13. Thanks!
Author
Owner

@ghost commented on GitHub (Nov 15, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 15, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15879