Update Fira Code fonts to 2.0 #372
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks |
LNKLEO
pushed a commit
to LNKLEO/Nerd
that referenced
this pull request
Nov 24, 2023
Update Fira Code fonts to 2.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fira Code just released a large update. I've updated the unpatched fonts with the new version.
Requirements / Checklist
../font-patcher src/unpatched-fonts/FiraCode/Regular/FiraCode-Regular.ttf --complete./gotta-patch-em-all-font-patcher\!.sh FiraCodeWhat does this Pull Request (PR) do?
Updates all unpatched fonts of FiraCode to the new version 2.
How should this be manually tested?
Checking out the PR and testing one of the new fonts (I tested Regular.ttf locally)