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

updated FiraCode to version 1.206 #298

Merged
merged 1 commit into from
Jan 25, 2019
Merged

Conversation

mashehu
Copy link
Contributor

@mashehu mashehu commented Oct 4, 2018

Description

I updated FiraCode to version 1.206 (by first exchanging the files in src/unpatched-fonts and then ran ./gotta-patch-em-all-font-patcher\!.sh FiraCode and manually updated the readme files afterwards).

Requirements / Checklist

  • Read the Contributing Guidelines
  • Read or at least glanced at the FAQ
  • Read or at least glanced at the Wiki
  • Scripts execute without error (if necessary):
    • If any of the scripts were modified they have been tested and execute without error, e.g.:
      • ./font-patcher Inconsolata.otf --fontawesome --octicons --pomicons
      • ./gotta-patch-em-all-font-patcher\!.sh Hermit
  • Extended the README and documentation if necessary, e.g. You added a new font please update the table

What does this Pull Request (PR) do?

Updates FiraCode to version 1.206

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)

screenshot 2018-10-04 15 45 47
Top shows some of the changed ligatures in FiraCode v1.206, bottom in v1.205.

@ryanoasis
Copy link
Owner

Thanks for this by the way, I will get it reviewed as soon as I can find some time

@ryanoasis ryanoasis added this to the v2.1.0 milestone Oct 21, 2018
@ryanoasis
Copy link
Owner

Will review...

@ryanoasis ryanoasis merged commit d9ea69a into ryanoasis:master Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants