Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Include Powerline Symbols #16

alexanderfahlke opened this Issue Sep 27, 2012 · 9 comments


None yet
5 participants

How about adding the "powerline" symbols to this very nice font?


I know how to patch my fonts manually, but it's a "complex" process for people who just want to start to use this font. I would really like to see these symbols in this font.

Source: https://github.com/Lokaltog/vim-powerline

I use it for some shell-eye-candy:



pauldhunt commented Sep 27, 2012

These don’t seem to be in Unicode 6.1, are these encoding slots being poached?


miguelsousa commented Sep 27, 2012

Yep. Those codepoints are not defined in 6.2 either http://www.unicode.org/charts/PDF/U2B00.pdf


pauldhunt commented Sep 27, 2012

Since these are poaching valid Unicode values (opposed to using PUA) I’m inclined not to add them to the main branch of the font.


miguelsousa commented Sep 27, 2012

Agree. Let's keep the issue open and see if anyone is interested in taking on the task.


pauldhunt commented Sep 27, 2012

btw, I posted this as an issue to Powerline: https://github.com/Lokaltog/vim-powerline/issues/223

@pauldhunt pauldhunt closed this Nov 28, 2012

Artanis commented Nov 28, 2012

It looks like the glyphs in question here will be moved into the private use area in an upcoming update to powerline, if I'm understanding the recent comments in Lokaltog/vim-powerline#128 correctly.

All the symbols have now been moved to the PUA in the upcoming version of Powerline: powerline/powerline@53fbfe1. Details available here.

@pauldhunt pauldhunt added fixed and removed DIY labels Jun 5, 2015


pauldhunt commented Jun 5, 2015

Powerline symbols will be in the next release of the fonts, which will likely be sometime in July.

@FocusedWolf FocusedWolf referenced this issue in andreberg/Meslo-Font Aug 11, 2015


Include Powerline glyphs #13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment