Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
vim-powerline patched fonts
This file has been truncated, but you can view the full file.

Awesome to the max

endel commented Jan 14, 2012

Awesome! Can you provide Monaco patched font too?

daqing commented Jan 14, 2012

+1 for patched Monaco

Thank you :D

suvash commented Jan 15, 2012

this is great, but what are the fontnames to be use on the vimrc file ? rather confused.

@suvash These fonts need to be installed in your machine, and then selected as your terminal font. You have to change nothing in your .vimrc (well, you need to activate the "fancy" mode, as the documentation says).

suvash commented Jan 15, 2012

Thanks a lot, and also found the trick for non-terminal vim(I use MacVim occasionally).

if has('gui_running')
  set guifont=Monaco:h12    " set fonts for gui vim
  set transparency=5        " set transparent window
  set guioptions=egmrt  " hide the gui menubar
endif

sjl commented Jan 17, 2012

If you want a version of Menlo that includes bold, italic, and bold italic: https://gist.github.com/1627888

Wish there was a Consolas patch.. :)

Owner

qrush commented Jan 18, 2012

Folks, I'm not going to provide any more patched fonts. I did the 3 up there for myself and a friend. Download vim-powerline, check out the readme, and get it working like I did if you want it with your own font.

Thanks for providing the fonts! I owe you a 🍺

mbadran commented Jan 20, 2012

Unrelated noob question: how do you attach a binary font file (ttf) to a gist? I patched Meslo DZ and I want to make it available.

sjl commented Jan 20, 2012

@ghost

ghost commented Jan 26, 2012

When using your patched Inconsolata font, and Powerline_symbols set to fancy, I get boxes instead of the patched characters. Here's a screenshot:

broken powerline status bar font

Is there a setting I'm missing, or is the font not working correctly? All my settings seem to be set to UTF-8 and using urxvt.

Edit: I've tried another font from the wiki, and it seems to work. This tells me the font you provide might not be functional.

@clownfart rm /tmp/Powerline.cache

@ghost

ghost commented Jan 26, 2012

@goatslacker that isn't a file. I've tried :PowerlineClearCache as well.

Edit: I was able to patch my own font, but the glyphs have a lower line height than Inconsolata-dz has. I will try with normal Inconsolata.

Thank you very much for those patched fonts. It saved my life (not able to compile on my MAC).

Font doesn't display correct in gvim, everything has wide spacings. Can anyone help?

niklas commented May 24, 2012

@6msj vim did not find the font. Try the following in your .vimrc:

set guifont=Inconsolata-dz\ for\ Powerline\ Medium\ 12

Excellent. Many Thanks.

My statusline looks strange with the Inconsolata font. This is in vim inside iTerm. It works just fine with MacVim

http://cl.ly/1M1C2T161E2D2S0f0w17

Have anyone got any idea?

I just downloaded Mensch and this is crazy.

supr commented Jul 3, 2012

@metamorfos i think you might have to increase the size of your status bar.

@metamorfos i think you might have to increase the size of your status bar.

that, amongst other things, did it @supr

J-Swift commented Sep 1, 2012

I had the same issue as metamorfos (using terminal vim and iTerm2) and found 2 ways to fix it. One, you can choose a different font. Two, you can mess with the vertical line height of the terminal font. Hope that helps someone.

dz commented Sep 13, 2012

Thanks much for the inconsolata-dz patch! :) I love powerline.

I just patched Inconsolata (after battling to get fontforge to compile). I made the following tweak to get the arrows to line up perfectly:

diff --git a/fontpatcher/fontpatcher b/fontpatcher/fontpatcher
index 2c54a3f..6e75838 100755
--- a/fontpatcher/fontpatcher
+++ b/fontpatcher/fontpatcher
@@ -177,7 +177,7 @@ for font_path in args.fonts:
        font.transform(psMat.translate(0, font_dim['ymax'] - sym_dim['ymax']))

        # Then move it the y center difference
-       font.transform(psMat.translate(0, sym_ycenter - font_ycenter))
+       font.transform(psMat.translate(0, sym_ycenter - font_ycenter - 66))

        # Ensure that the glyph doesn't extend outside the font's bounding box
        if sym_dim['width'] > font_dim['width']:

Love to see this for Adobe's new Source Code Pro.

joshmosh commented Oct 5, 2012

  • 1 for Monaco

ruaz commented Nov 26, 2012

@davidchambers Excellent work, thank you! Finally, I have a decent looking status bar.

hit9 commented Jan 1, 2013

cool, i like it !

zhm commented Feb 11, 2013

I ended up having to make some tweaks to the fontpatcher script to get Inconsolata-dz to line up perfectly in MacVim.

Here is my font file for anyone else who stumbles upon this: http://cl.ly/3Q362Q2M1e1h

Enabled using set guifont=Inconsolata-dz\ for\ Powerline:h13

Here are my changes to the fontpatcher script:

diff --git a/fontpatcher/fontpatcher b/fontpatcher/fontpatcher
index 2c54a3f..4826d9d 100755
--- a/fontpatcher/fontpatcher
+++ b/fontpatcher/fontpatcher
@@ -164,7 +164,7 @@ for font_path in args.fonts:
                        # Stretch the glyph vertically
                        scale_ratio = font_dim['height'] / sym_dim['height']

-                       font.transform(psMat.scale(1, scale_ratio))
+                       font.transform(psMat.scale(1, scale_ratio * 1.3))

                # Use the dimensions from the pasted and stretched glyph
                sym_dim = get_dim(font[sym_glyph.unicode])
@@ -177,7 +177,7 @@ for font_path in args.fonts:
                font.transform(psMat.translate(0, font_dim['ymax'] - sym_dim['ymax']))

                # Then move it the y center difference
-               font.transform(psMat.translate(0, sym_ycenter - font_ycenter))
+               font.transform(psMat.translate(0, sym_ycenter - font_ycenter + 60))

                # Ensure that the glyph doesn't extend outside the font's bounding box
                if sym_dim['width'] > font_dim['width']:

dvcrn commented Jun 26, 2013

Can someone update these fonts to the new code points? robbyrussell/oh-my-zsh#1872

justin8 commented Jul 6, 2013

You can get the menlo patched font at least from my dotfiles here:
https://github.com/justin8/dotfiles/tree/master/install-files/fonts

I couldn't find a decent font with the new code points, so I ripped the menlo ttc from OS X and patched it.

The best source for the updated fonts seems to be https://github.com/Lokaltog/powerline-fonts

tgy commented Nov 6, 2013

@justin8 your Menlo font is not working

Can someone provide a Menlo patched font please ?

@Toogy Not sure if this works for you, but this copy of Menlo seems to have solved the problem for myself.

mtalebi commented Mar 7, 2014

I don't know if this helps anyone else, try changing your iTerm's profile to Pastel (Dark Background). It fixed the icon display issue for me. My terminal now looks exactly like http://www.paradox.io/posts/9-my-new-zsh-prompt. FYI, I did install the above fonts.

Superlative work!

trusktr commented Dec 27, 2014

These fonts don't seem to work? I just installed these, along with Prezto, then when I choose one of these fonts in iTerm2, the font changes in the terminal, but the ugly symbols remain (I don't see the nice powerline triangles).

I have the same problem as trukstr. I installed the fonts from https://github.com/powerline/fonts but not all icons are shown correctly

@ghost

ghost commented Jul 12, 2015

Thank you!

topdown commented Jun 16, 2016 edited

Once you go through the font installation you need to set the fonts in whatever you are using for that profile.
For me it was iTerm2 on latest Mac OSx
Go to preferences > select the profile you are using > Text tab
Now set both the Font and Non-ASCII Font to one the ends in Powerline.
screen shot 2016-06-16 at 1 35 32 pm

If there are not fonts that end in Powerline it is not installed correctly.
Frankly with all of the issues I was surprised I got it to work in 2016 :)

screen shot 2016-06-16 at 1 34 55 pm

Yammmy commented Dec 6, 2016

Thx :)

suilu commented Dec 15, 2016

Thank you!

awesome~

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