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
The Hasklig recently released version 1.2 which addresses the issues outlined in microsoft/vscode#100840. The summary of that issue is that macOS Big Sur brought some subtle changes that meant that a lot of fonts broke in VSCode, showing only black text.
This PR brings the new version into nerd-fonts along with the patches applied to the new version.
Requirements / Checklist
./font-patcher Inconsolata.otf --fontawesome --octicons --pomicons
./gotta-patch-em-all-font-patcher\!.sh Hermit
What does this Pull Request (PR) do?
Updates the Hasklig font to version 1.2, which brings important bug fixes.
How should this be manually tested?
Update your font and include it in VSCode. All now works.
Any background context you can provide?
Motivation behind the update, besides being up-to-date itself, is to fix microsoft/vscode#100840.
What are the relevant tickets (if any)?
microsoft/vscode#100840
Screenshots (if appropriate or helpful)
N/A