Git Product home page Git Product logo

awesome-terminal-fonts's Introduction

Why?

Why do you want to use fancy symbols in your standard monospace font? Obviously to have a fancy prompt like mine :-)

prompt

And 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

Heavily inspired by https://github.com/Lokaltog/vim-powerline and the relative patch script from Kim Silkebækken ([email protected])

Patching vs Fallback

There are two strategies that could be used to have symbols in a terminal

  • you can take a bunch of symbol fonts, your favourite monospace font and merge them together (patching strategy)
  • you can use a feature of freetype2 font engine, basically you can say that whenever the current font doesn't have a glyph for a certain codepoint then fallback and go look into other fonts (fallback strategy)

Initially I used the first strategy, later I switched to the second. The patching strategy it's 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's a lot of manual fine tuning. If you want you can find all previous patched fonts in patching-strategy branch

Font Maps

Referring to glyphs by codepints (eg. \uf00c) in your scripts or shell configuration it's not recommended because icon fonts like Font Awesome use code points ranges those ranges are not disciplined by the unicode consortium, every font can associate every glyphs to those codepoints. This means that Font Awesome 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 one icon font can use the same codepoint for different glyphs and if we want to use them both we need to move one of them. So, if you use a codepoint to refer to a glyph after an update that codepoint can point to another glyph. To avoid this situation you can use the font maps in the ./build directory, font maps are scripts which define shell variables that give names to glyphs, by sourcing those files in your shell you can refer to glyphs by name (eg. $CODEPOINT_OF_AWESOME_CHECK).

TLDR: don't refer to glyphs by codepoints (eg. \uf00c) but by name (eg. $CODEPOINT_OF_AWESOME_CHECK) to make your scripts and shell configurations resilient to future updates. To do that don't forget to copy font maps (*.sh files) in the ./build directory in your home directory and to source them in your shell startup

Included Fonts

In this repository you can find a bunch of fonts that I use as symbol fonts with the relative font maps

How to install (Linux)

  • copy all the fonts from ./build directory to ~/.fonts directory
  • copy all the font maps (all *.sh files) from ./build directory to ~/.fonts directory
  • run fc-cache -fv ~/.fonts to let freetype2 know of those fonts
  • customize the configuration file ./config/10-symbols.conf replacing PragmataPro with the name of the font you want to use in the terminal (I will add more fonts in the future so that this step could be skippable)
  • copy the above configuration file to ~/.config/fontconfig/conf.d directory
  • source the font maps (source ~/.fonts/*.sh) in your shell startup script (eg. ~/.bashrc or ~/.zshrc)

Arch Linux

We have been included in the official repositories, so if you are running an Arch Linux

  • run pacman -Syu awesome-terminal-fonts

How to install (OSX)

  • follow this detailed instructions contributed by @inkrement
  • copy all the fonts maps (all *.sh files) from ./build directory to ~/.fonts directory
  • source the font maps (source ~/.fonts/*.sh) in your shell startup script (eg. ~/.bashrc or ~/.zshrc)
  • If it still doesn't work, consider to use the patching strategy

How to install (Windows)

  • make sure you have permissions to execute Powershell scripts in your machine. To do so, open Windows Powershell as Administrator and paste & run the following command Set-ExecutionPolicy RemoteSigned
  • then run the install script ./install.ps1

License

MIT

awesome-terminal-fonts's People

Contributors

gabrielelana avatar iandundas avatar jnardiello avatar leandrocrs avatar sdevmaster avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

awesome-terminal-fonts's Issues

How do I see all the fonts with their codepoints?

Silly question, but how do I list all the symbols in the font files? I can see that in the build.sh files they are listed with their names, and I can use ctrl-shift-u to enter the codepoint, but is there some kind of program that I could use to see all of them?

I have tried looking at the pomodoro font with gucharmap, but I can't find the added symbols? Perhaps because they are in the private area?

Fallback strategy not working

After follow the instructions and the comments in #20 I get to the following point:
1 - octoicons are not found
2 - descriptive encoding of the icons des not work

sik@Nekyia:~$ fc-list | ack -i "icons|awe"
/home/sik/.fonts/devicons-regular.ttf: icomoon:style=Regular
/home/sik/.fonts/fontawesome-regular.ttf: FontAwesome:style=Regular
/home/sik/.fonts/pomicons-regular.ttf: Pomodoro:style=Regular
sik@Nekyia:~$ echo -e "\u$CODEPOINT_OF_AWESOME_TWITTER"
\u
sik@Nekyia:~$ echo -e "\uf099"

Devicons: code point ("Gopher") overwritten by Greek symbol ("Sigma")

Hi,
I'm not quite sure if this is a borked setup on my side or something wrong with this package/one of its dependencies, but my hope is we can figure this out here together rather than me rage-typing into search engines.

I'm running Arch Linux and currently using the AUR package provided, which builds straight from this repo; however, the official package shows the same behaviour.

Recently (~1 week ago) I noticed two icons I was using in my statusbar differed from what they should be, namely the lower-case lambda, and the Golang Gopher icon provided by the Devicons icon set. This probably co-incided with one of the semi-regular VCS rebuilds I run on my system, which rebuilds all packages based directly off an upstream repo, including this one.

The lambda came back (somehow, don't know how, don't really mind), yet the Gopher is still missing. According to the cheatsheet, the icon uses codepoint \e624. When I type echo "\ue624", and when I look at my statusbar, this shows the greek upper-case Sigma:

2018-03-02-124308_197x63_scrot

Incidentally, I see similar behaviour for all other code points in Devicons, Octicons and Pomicons, yet FontAwesome works just fine.

Any idea what this could be related to? I'm CC'ing @shibumi as they provided the Arch package and might know the ins and outs.
My hunch is that I have some font that is using those code points, but I did not consciously install any...
Thanks, and have a great day! :)

Fonts not visible on ubuntu

Hello,

The fonts are not visible in the terminal configuration (Edit > Profiles > Edit current ...).
I have tried to place the fonts in ~/.fonts/ or /usr/share/fonts/truetype.

I followed the instructions from the oh-my-git doc:

# Copy the awesome fonts to ~/.fonts
cd /tmp
git clone http://github.com/gabrielelana/awesome-terminal-fonts
cd awesome-terminal-fonts
git checkout patching-strategy
mkdir -p ~/.fonts
cp patched/*.ttf ~/.fonts

# update the font-info cache
sudo fc-cache -fv ~/.fonts

Any idea?

need instructions in doc on how to work with fallback method or test

Hello,

I had installed this package from Arch's repo but am having trouble seeing whether it works or not. I thought since it's included in the official repo that Arch would include direction if not a trail of links to follow.
I checked /etc/fonts/10-symbols.conf and saw the following after installing the package:

<fontconfig>
  <alias>
    <family>PragmataPro</family>
    <prefer>
      <family>Pomodoro</family>
      <family>FontAwesome</family>
      <family>Octicons</family>
      <family>Icomoon</family>
    </prefer>
  </alias>
</fontconfig>

so I copied and pasted the above to a newly created file: ~/fontconfig/fonts.conf, following advice that I got from irc. Thanks for your work.

So it's still impossible to get a job right now

I installed this font, and I set it, but the icon shows "? "This looks like this

I feel that you are in the configuration, writing very vague, resulting in many people installation is not successful... I hope you see this feedback. You can maintain your documents. To help more people use it

.fonts not a directory

I'm getting the above error when trying to "copy all the fonts from ./build directory to ~/.fonts directory"

Missing list of supported/tested terminal emulators

It would be nice to have a list of supported terminals, because having FA in terminal is great, but on some terminals it is just not usable at all. Screenshot taken using Konsole:

konsole
the biggest issue i have is

  • letters like p , g , y or q are trimmed at the bottom and it makes really difficult type commands or, even worse, read/edit files;
  • did you notice the gap between the path /usr/local/bin and _ ? it's just one space. For some reason, using FA on Konsole misplaces the cursor in such a way that, the more characters you type, the wider becomes the gap. Which makes editing typos in the middle of the line very difficult
    screenshot_20170826_182314

So yeah, please add which terminals are proven to be working with FA, so I (and others too) can switch to it ;-)

Unable to make the font work on Ubuntu

I followed the instructions but it does not seem to work. I'm on Ubuntu 15.10.

I read #11, I can see the icon if I enter echo "\uf20c" in a terminal. I tried to move 10-symbols.conf to /etc/fonts/conf.d/ with no success

Provide examples

Hello,
Would it be possible to provide examples (like a git prompt?)

That would be really helpful

Cannot stat ./.work/octicons-regular-relocated.ttf

fu-relocate is redirected 2>/dev/null so any failure is displaced to the next dependent line, in this case build.sh:13 (fu-relocate ...) to build.sh:14 (cp ...).

Appending || { echo "Failed for ..." && exit 1 } to each command shows me that the first invocation of fu-relocate failed... and removing the redirection to /dev/null shows that I was missing FontForge.

Possible fixes:

which fontforge >/dev/null || echo "Missing FontForge" && exit 1 (most portable?)

[ -x /usr/bin/fontforge ] || echo "Missing FontForge" && exit 1 (depends on location)

dpkg -l | grep fontforge || echo "Missing FontForge" && exit 1 (depends on dpkg)

Can't get it to work on OSX

This is what I am doing:

$ which fc-cache
/usr/local/bin/fc-cache

$ git clone https://github.com/gabrielelana/awesome-terminal-fonts.git
$ cd awesome-terminal-fonts

$ ./install.sh

$ ls ~/.fonts
devicons-regular.sh
devicons-regular.ttf
fontawesome-regular.sh
fontawesome-regular.ttf
octicons-regular.sh
octicons-regular.ttf
pomicons-regular.sh
pomicons-regular.ttf

I have iTerm2 set up to use Meslo LG M Regular for Powerline, so I made ~/.config/fontconfig/conf.d/10-symbols.conf look accordingly:


<fontconfig>
  <alias>
    <family>Meslo LG M Regular for Powerline</family>
    <prefer>
      <family>Pomodoro</family>
      <family>FontAwesome</family>
      <family>Octicons</family>
      <family>Icomoon</family>
    </prefer>
  </alias>
</fontconfig>

Let's check if fc-list sees Meslo LG M Regular for Powerline:

$ fc-list | grep 'Meslo LG M Regular for Powerline'

/Users/jottr/Library/Fonts/Meslo LG M Regular for Powerline.otf: Meslo LG M for Powerline:style=RegularForPowerline

Let's check if fc-list sees pomicons-regular:

$ fc-list | grep Pomodoro
/Users/jottr/.fonts/pomicons-regular.ttf: Pomodoro:style=Regular

Let's check if anything from ~/.fonts/fontawesome-regular.sh is available in the shell:

$ echo '\uf00c'


Nope. Nothing.
Running ./build.sh first does not help either.

Also, a cursory check seems to indicate that some symbols, i.e. fa-hourglass seem to be missing from fontawesome-regular.sh.


iTerm2 Build 2.9.20160206

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.11.3
BuildVersion:   15D21

$ zsh --version
zsh 5.2 (x86_64-apple-darwin15.0.0)

SourceCodePro+Powerline+Awesome Not working in Chrome 55 on Win10

I'm trying to use the fonts with Secure Shell in Chrome, and they're not displaying properly. At first I thought it was my installation/method of usage, but after setting my mono-spaced font to SourceCodePro+Powerline+Awesome in the Chrome preferences, I'm beginning to think this is a Chrome incompatibility.

It displays fine in the preferences preview:
snip1
But when it comes to actually displaying text on a page, it fails:
snip2

If this is a Chrome issue, then so be it, but other iterations of SouceCodePro work without an issue in hterm (Secure Shell), so I'm not 100% sure where the problem lies. If there's anything else I should try, let me know.

font mapping broken

Hello,
The last stable commit was fcfef52 every commit after this is broken due to font mapping issues.
When I apply any other commit after this my zsh powerline seems broken.

Screenshots:

Everything fine:
..

Broken:
..

I have no idea if this is the fault of zsh-theme-powerlevel9k or of awesome-terminal-fonts.

[Question] Name of the font

What is the name of Source Code Pro Powerline Awesome font (patched one)? I want to use it my editor (VS Code), in which I had to type the name of the font to use it, but I am not able to get its right name. :-/

Patched version in microsoft windows

I'm stuck with windows at work, I tried your patched branch, but without luck, Mintty refuses to see the patched fonts, there is no chance to use them or there is another way to patch them?

macOS Sierra can't display font.

After update my Mac to macOS Sierra, the font in iTerm2 can't display anymore.
In Font Book, the fontawesome can't display right too.
screen shot 2016-09-21 at 3 50 48 pm

Icons are huge in Operator Mono

I tried patching Hoefler Operator Mono but the icons are huge. It doesn't seem like the patch script is respecting the ratios. I'm using a version of Operator Mono SSm that I patched with the Powerline icons.

This is how I modified one of the existing patch scripts.

#!/bin/sh
cp ./fonts/OperatorMonoSSmBook+for+Powerline.otf S0.ttf
./patch S0.ttf --symbols=./fonts/fontawesome-webfont.ttf --to-namespace=AWESOME --rename-as=S1 --starting-at='0xe100' --ratio=0.75 --shift-x=100 --shift-y=50
./patch S1.ttf --symbols=./fonts/octicons-regular.ttf --to-namespace=OCTICONS --rename-as=S2 --starting-at='0xe800' --ratio=0.75 --shift-y=25
./patch S2.ttf --symbols=./fonts/pomicons-regular.ttf --to-namespace=POMICONS --rename-as='OperatorMonoSSmBook+for+Powerline+Awesome' --starting-at='0xf000' --ratio=0.5 --shift-x=-100 --shift-y=25
cat S1.sh S2.sh >> OperatorMonoSSmBook+for+Powerline+Awesome.sh
cp OperatorMonoSSmBook+for+Powerline+Awesome.* ~/.fonts
mv OperatorMonoSSmBook+for+Powerline+Awesome.* ./patched
sudo fc-cache -rv
rm -rf S?.*

please use release system

Hello,
It would be awesome if you could use the release system. I am working on a package for Arch Linux.
So that everybody can install your fonts more easier.

Thanks!

There's a better way

I think there's a better way for fontawesome to be used in terminal.
Just install FontAwesome.otf file and fix .Xresources:

*faceName: inconsolata, font-awesome

No need to patch existing fonts.
No need to support them all (there are ~30 popular terminal fonts).

Add font-linux

https://github.com/Lukas-W/font-linux

Alternatives to the penguin glyph would be nice :)


Probably not the right place, but few questions.

I came across this SourceCodePro + Powerline + Awesome Regular font, it seems to be custom patch by the user. Would you know if the Awesome bit was referring to this repo or Font Awesome?

With the fallback strategy, is the only benefit this repo provides a font map? I noticed some of the fonts haven't been updated in a while like with other repo's. Rendering wise, if fallback works would be effectively the same as having those glyphs patched together as a single font or are there potential differences?

OSX doesn't seem to support the fallback option from what I'm reading, and some terminals/OS have rendering issues where I assume fallback strategy won't be enough? Besides adding the glyphs to merge into a base font, how much work/time can be involved to fix those offset/size issues I've seen around the place? These official patched versions seem quite outdated: https://github.com/powerline/fonts , not sure how much that matters.

Fonts not working on zsh themes

I installed the fonts as described (fallback strategy), used antigen for oh-my-zsh, oh-my-git and themes) but still haven't got the fonts working, even though I can see the characters when using echo.

screenshot from 2017-02-08 11-36-41

I'm using CentOS and RedHat on that (tested on multiple servers).

Fonts specified in 10-symbols.conf break the font if used in Firefox. Font renders as seemingly random symbols.

I have the following two fonts specified in my 10-symbols.conf file to use the awesome-terminal-fonts:

<fontconfig>
  <alias>
<family>FiraCode</family>
<prefer>
  <family>Pomodoro</family>
  <family>FontAwesome</family>
  <family>Octicons</family>
  <family>Icomoon</family>
</prefer>
  <alias>
<family>Roboto</family>
<prefer>
  <family>Pomodoro</family>
  <family>FontAwesome</family>
  <family>Octicons</family>
  <family>Icomoon</family>
</prefer>

If either of these fonts are set as one of the default fonts in Firefox, the fonts render as random symbols in Firefox. Not just the extra symbols, but regular letters and numbers too.

Elsewhere on the system, both fonts render fine, with the additional font symbols rendered as expected.

Not sure how to fix this. Is this an issue with Firefox or my 10-symbols.conf?

The font still not working for OSX

I followed the instruction but nothing happened. I want to use an octicon git-branch. I also use the font PragmataPro as my default font in terminal as well as vim.

Here is my set up

  1. copy 3 fonts from ./build into .fonts directory
  2. run fc-cache -fv ~/.fonts
  3. copy file ./config/10-symbols.conf to ~/.config/fontconfig/conf.d

Because I use PragmataPro as my font so I leave the config file as it was.
But after did all of these things, nothing happened. I still miss octicon git-branch.

Did I missed?

Official Arch Linux package

Hello,
Just want to inform you that I have pushed your last release to the official arch linux repositories.
Users can now install your font directly via pacman -Syu awesome-terminal-fonts.

Fallback osx iterm

Hi, sorry i do not understand what i have to do on this instruction:

  • source the font maps (source ~/.fonts/*.sh) in your shell startup script (eg. ~/.bashrc or ~/.zshrc)
    Can you help me? thanks.

Awesome Powerline Fonts dose not worked

this is my .zshrc content:

# Path to your oh-my-zsh installation.
# Path to your oh-my-zsh installation.
export ZSH=/Users/rlanffy/.oh-my-zsh

# Set name of the theme to load.
# Look in ~/.oh-my-zsh/themes/
# Optionally, if you set this to "random", it'll load a random theme each
# time that oh-my-zsh is loaded.
#ZSH_THEME="agnoster"
ZSH_THEME="powerlevel9k/powerlevel9k"
DEFAULT_USER=""
POWERLEVEL9K_MODE='awesome-patched'
#POWERLEVEL9K_MODE='flat'
POWERLEVEL9K_PROMPT_ON_NEWLINE=true
#POWERLEVEL9K_MULTILINE_FIRST_PROMPT_PREFIX="↱"
#POWERLEVEL9K_MULTILINE_SECOND_PROMPT_PREFIX="↳ "

# Uncomment the following line to use case-sensitive completion.
# CASE_SENSITIVE="true"

# Uncomment the following line to use hyphen-insensitive completion. Case
# sensitive completion must be off. _ and - will be interchangeable.
# HYPHEN_INSENSITIVE="true"

I installed pro like how to install as your said.

when the config is POWERLEVEL9K_MODE='awesome-patched' and the terminal is like this:
terminal1

when the config is POWERLEVEL9K_MODE='flat' and the terminal is like this:

terminal2

Any tips for fonts not showing up in rxvt?

I'm using rxvt-unicode, and I can't get the fonts to show up, with the fallback method. I'm trying

echo -e "\uf175"

But this produces a square in rxvt. If I try it in xfce4-terminal, it works fine.

installation difficulties on linux

with solo user install and multi user install for powerline fonts i have 10-symbols.conf in multiple folders and i am getting lost about wich is effective. Also when you say "replacing PragmataPro with the name of the font you want to use in the terminal " you talk about one of the 4 fonts available in the .buid ? I'm sorry it seems a stupid question but this is not obvious for me, and i have also to integrate it with Powerlevel9K that is not obvious too. I know when i'll succeed it i'll say it was obvious but now i'm lost and search a little help here after posting a lot of post in askUbuntu ^^

I'll delete this post as fast as i receive an answer that direct me a little as this is not a real issue .... sorry

Fallback strategy not working

Hi, first of all, thank you for the great work.

I am trying to install the fonts via the fallback strategy, but seems not to work and I gave up and install via patch. But I would like to install the first method. Here is what I am doing:

I've followed the steps in the README, but does not work. So I tried to install the fonts in /usr/share/fonts/truetype, and put the 10-symbols.conf in /usr/share/fontconfig/conf.d/.

Later I run fc-cache -fv /usr/share/fonts, as root, but nothing seems to work.

My 10-symbols is:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">

<!--
When a glyph is missing in the current font freetype2 will look into
other installed fonts to see if it's going to find it, but which fonts?
and in which order?

The configuration below aim to declare an ordered list of fonts
to be looked into when a glyph is not found in a specic font

<alias>
  <family>FONT_WITH_A_POSSIBLY_MISSING_GLYPH</family>
  <prefer>
    <family>FIRST_FONT_TO_LOOK_INTO</family>
    <family>SECOND_FONT_TO_LOOK_INTO</family>
    <family>...</family>
  </prefer>
</alias>
-->

<fontconfig>
  <alias>
    <family>Ubuntu</family>
    <prefer>
      <family>FontAwesome</family>
      <family>Pomodoro</family>
      <family>Octicons</family>
    </prefer>
  </alias>
</fontconfig>

I've also tried with Ubuntu Mono and UbuntuMono.

I am using Linux Mint Debian Edition.

Any ideas?

Best regards

Insert font: Source Code Pro

One suggestion is to put the power of the Adobe Source Code, which is a source made ​​especially for development.

Patching Font Terminus

I don't understand how can patch my font.

In the past I patched Terminus as Powerline, but now i want to embed the awesome chars, can you help me to know what is the way to patch with this fonts to my Terminus Powerline.

I reused the code into the droid.sh, and i don't get erros, so I continue with the installation using the FontBook. And I set the font into Iterm2, the problem is not rendered the right chars.

Here my fonts.
Terminus.ttf
Terminus-Powerline.ttf

License

What is the license of your project ? And what are the fronts licenses provided in the fonts directory ?

It could also be nice to reference those fonts in the README.md

Regards,
Fabien

Issues with fall back fonts and Yosemite

I've followed the directions in the install section but OS X still doesn't seem to honor the fallback font config for freetype

echo "\uf20c"


Any suggestions on getting this working ?

Fontawesome 4.7.0

Could you please update fontawesome to 4.7.0, so that there is support for the new icons?

bad render on MacOS

I have installed the fonts and I see them, but I can't seem to get them to render properly. They appear to be somewhat jagged.

I am using Iconsolata for Powerline 14pt and you can see what I am talking about here:
screen shot 2018-05-09 at 12 45 41

Thank you in advance for any guidance/help.

How much of the setup instructions are relevant to arch linux?

Arch Linux has this in it's repo, so does Manjaro. I'm using Manjaro, and I installed the package. I am able to use the fonts. But I was confused regarding what part of the the installation instructions I need to follow. Also the directories change, so I had to make some minor changes to commands.

  1. Fonts are in /usr/share/fonts/awesome-terminal-fonts. Looks like the package copies them here.
  2. .sh files already present in above directory
  3. rebooted instead of fc-cache command. Didn't try it
  4. config is in /etc/fonts/conf.d/10-symbols.conf. Replaced font to Hack using root permissions. (I guess this was unnecessary, I should have copied and made change only to local file)
  5. copied the above configuration file to ~/.config/fontconfig/conf.d, had to create that directory first.
  6. Added source command to zsh and bash rc files.

I guess I did it right, still wanted to verify. Also, is there any specific powerline theme that makes use of these icons? How does one make use of these icons?

Availability of other fonts

Hi,

I would like to use e.g the "Menlo Regular for Powerline" in combination with the awesome fonts.
As far as I understand I would need to patch these myself?
Is there a a simply way to do this?

Applying font fallback on Mac OS X?

I wish to use Pomicons on iTerm2 in Mac OS X.

If understood correctly I need to copy fonts from build to ~/Library/Fonts (instead of to ~/.fonts).

But I'm not sure where to put the 10-symbols.conf, provided that Mac OS X font system can understand this fontconfig file.

For now I'm working around this issue using the "Non-ASCII Font" fallback of iTerm2 but this is not a very good solution as you can add only just one font alternative.

I know about nothing about Fonts and how Fonts works on Mac OS X, and I'm also having some difficult in understand what to search on Google to find a solution, any help will be appreciated.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.