Build for Nerd Fonts v3 (a breaking change) #9
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
|
@Karmenzind tagging you in case you weren't notified |
|
sorry for the late |
|
@hjdarnel Thanks for your work! |
|
@Karmenzind I pulled it from my system fonts (on macOS) so fontmirror.com should be a good link to it. |
|
@hjdarnel thanks :) |
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.
Nerd Fonts recently released a v3 which is causing plugins that use a Nerd Font to upgrade. Unfortunately this means if you don't have an updated v3 Nerd Font, stuff starts breaking (like here).
I removed the now unnecessary
--also-windowsflag from the build script, as both fonts should now be Windows compatible (see here for that change). I also rebuilt the font and validated that it works correctly after installing.