Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for installation of fonts #166

Open
sob opened this issue May 15, 2020 · 12 comments
Open

Support for installation of fonts #166

sob opened this issue May 15, 2020 · 12 comments
Assignees
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone

Comments

@sob
Copy link

sob commented May 15, 2020

Description of the new feature/enhancement

As part of a new system build, I typically install a handful of fonts including Cascadia Code and other powerline enabled fonts. These fonts don't have an installer associated with them but instead need to be manually downloaded, extracted, and installed.

https://github.com/microsoft/cascadia-code/releases

@sob sob added the Issue-Feature This is a feature request for the Windows Package Manager client. label May 15, 2020
@denelon denelon added this to the Package Manager Backlog milestone May 16, 2020
@TravisSpomer

This comment has been minimized.

@RobCannon
Copy link

Be sure to enable installing a font as a non-admin user!

@BatmanAoD
Copy link

Installing a CLI font manager might be acceptable.

@weitzhandler
Copy link

weitzhandler commented Jul 9, 2020

Related:


Installing a CLI font manager might be acceptable.

Not my preference. There should maybe be a special flag for fonts, but not another font manager.

@WSLUser
Copy link

WSLUser commented Jul 30, 2020

Neither are needed. All that's needed is for the font to be uninstalled first, then the updated version is installed after. Some apps or stuff in Windows will need a font-fallback during this process if they're configured to use that font. So winget just needs to support the unattended uninstallation and installation of the font.

@denelon denelon modified the milestones: Package Manager Backlog, Package Manager v0.30.x Aug 24, 2020
@denelon
Copy link
Contributor

denelon commented Mar 22, 2021

Adding the link to Cascadia Code and a mention to @cinnamon-msft

@denelon denelon modified the milestones: Package Manager v0.30.x, Package Manager Backlog, Backlog - Windows Package Manager, v.Next - Windows Package Manager May 3, 2021
@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Nov 16, 2021

Because the Microsoft Store is able to manage this already, implementation of this feature is important for compatibility with it. This was the purpose of the addition of the "msstore" repository additionally.

@denelon
Copy link
Contributor

denelon commented Jun 3, 2022

Hey everyone oh-my-posh by @JanDeDobbeleer now has support for installing nerd fonts.

@musm
Copy link

musm commented Jun 3, 2022

Hey everyone oh-my-posh by @JanDeDobbeleer now has support for installing nerd fonts.

How does that relate to winget?

@denelon
Copy link
Contributor

denelon commented Jun 3, 2022

I assume there are Windows Package Manager users who are generally interested in being able to install fonts with a CLI. As we haven't sequenced when this feature might land, I was trying to be helpful for the community by offering one possible solution that could be used "today".

Related to:

@beingmerry
Copy link

This would be a great feature to have. I use OhMyPosh so I'll use that workaround for now.

@denelon
Copy link
Contributor

denelon commented May 30, 2024

I've started a discussion on fonts. Please don't add any additional comments to this Issue to avoid the large number of people who receive e-mail notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
Status: In Progress
Development

No branches or pull requests