Awesome Terminal Fonts

{
  "alternatives": [],
  "artifacts": [
    {
      "font": [
        "awesome-terminal-fonts-patching-strategy/patched/Droid+Sans+Mono+Awesome.ttf"
      ],
      "target": "/$HOME/Library/Fonts/Droid+Sans+Mono+Awesome.ttf"
    },
    {
      "font": [
        "awesome-terminal-fonts-patching-strategy/patched/Inconsolata+Awesome.ttf"
      ],
      "target": "/$HOME/Library/Fonts/Inconsolata+Awesome.ttf"
    },
    {
      "font": [
        "awesome-terminal-fonts-patching-strategy/patched/SourceCodePro+Powerline+Awesome+Regular.ttf"
      ],
      "target": "/$HOME/Library/Fonts/SourceCodePro+Powerline+Awesome+Regular.ttf"
    }
  ],
  "auto_updates": null,
  "categories": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": null,
  "disable_reason": null,
  "disabled": 0,
  "display_name": "Awesome Terminal Fonts",
  "enrichment_fetched_at": "2026-06-20T22:43:00+00:00",
  "first_seen": "2026-06-20T00:47:34+00:00",
  "full_token": "font-awesome-terminal-fonts",
  "github_default_branch": "master",
  "github_last_commit_at": "2024-01-16T06:56:48Z",
  "github_readme_excerpt": "# Why?\nWhy do you want to use fancy symbols in your standard monospace font? Obviously to have a fancy prompt like mine :-)\n\n![prompt](https://github.com/gabrielelana/awesome-terminal-fonts/raw/master/why.png)\n\nAnd because when you live in a terminal a symbol can convey more informations in less space creating a dense and beautiful (for those who have a certain aesthetic taste) informative workspace\n\nHeavily inspired by \u003chttps://github.com/Lokaltog/vim-powerline\u003e and the relative patch script from **Kim Silkeb\u00e6kken** (kim.silkebaekken+vim@gmail.com)\n\n## Patching vs Fallback\nThere are two strategies that could be used to have symbols in a terminal\n* you can take a bunch of symbol fonts, your favourite monospace font and merge them together (patching strategy)\n* you can use a feature of `freetype2` font engine, basically you can say that whenever the current font doesn\u0027t have a glyph for a certain codepoint then fallback and go look into other fonts (fallback strategy)\n\nInitially I used the first strategy, later I switched to the second. The patching strategy it\u0027s more reliable and portable, the problem is that you need to patch every monospace font you want to use and patching a single font it\u0027s a lot of manual fine tuning. If you want you can find all previous patched fonts in [patching-strategy branch](https://github.com/gabrielelana/awesome-terminal-fonts/tree/patching-strategy)\n\n## Font Maps\nReferring to glyphs by codepints (eg. `\\uf00c`) in your scripts or shell configuration it\u0027s not recommended because icon fonts like [Font Awesome](http://fontawesome.io/) use [code points ranges](https://en.wikipedia.org/wiki/Private_Use_Areas) those ranges are not disciplined by the unicode consortium, every font can associate every glyphs to those codepoints. This means that [Font Awesome](http://fontawesome.io/) can choose to move glyphs around freely, today `\\uf00c` is associated to the `check` symbol, tomorrow it can be associated to something else. Moreover, more than o",
  "github_repo": "gabrielelana/awesome-terminal-fonts",
  "github_stars": 2524,
  "github_topics": [],
  "homepage": "https://github.com/gabrielelana/awesome-terminal-fonts",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 95,
  "installs_365d": 1224,
  "installs_90d": 328,
  "last_seen": "2026-06-20T00:47:34+00:00",
  "llm_generated_at": null,
  "llm_model": null,
  "names": [
    "Awesome Terminal Fonts"
  ],
  "one_liner": null,
  "rank_30d": 1434,
  "rank_365d": 1287,
  "rank_90d": 1331,
  "raw_hash": "f05f1b2ab8def9f0",
  "ruby_source_path": "Casks/font/font-a/font-awesome-terminal-fonts.rb",
  "tap": "homebrew/cask",
  "token": "font-awesome-terminal-fonts",
  "version": "latest",
  "why_use_this": null
}