Can't see symbols in vim but present in tmux about powerline HOT 8 CLOSED

The glyph code points have changed in this version. Are you using a font patched with the new font patcher (some examples are in my powerline-fonts repo).

from powerline.

Thanks for the reply

I've manually generated patched fonts to no avail

When validating the fonts in your powerline-repo File > Validate File option in font book, it reports errors with all fonts (except the Menlo regular) - however installing these does not seem to resolve the issue

Any ideas?

/Matt

from powerline.

What makes me think that you have a legacy font installed is that you use Steve Losh's(?) tmux statusline, and last time I checked it used the legacy code points for arrow symbols. This project uses different code points and a different font patcher. If you open your font in a character map application, are you able to see the arrow glyphs in code points U+E0B0-U+E0B3?

from powerline.

You're absolutely right about the status line - i'm looking at it now and actually if I remove that legacy entry with your recommended tmux config ( set-option -g status-right "#(powerline-tmux right)" ) the status bar all but dissapears

Are you able to recommend a character map application to test?

Many thanks

/Matt

from powerline.

I'm using Linux and I don't know what's available in OS X, but if the glyphs disappear when you're using tmux-powerline you're using a font patched with the legacy font patcher and you need to update your font (if you're using iTerm2 you'll also have to update to this version or later). Try to replace your current version of "Inconsolata for powerline" with this font version and see if that works.

from powerline.

Thanks very much for the updated font - it makes no difference when using that one so I think I can definitely rule the font out - I think however its likely to be the iTerm2 issue now possibly - I am currently using the latest version from http://code.google.com/p/iterm2/downloads/list so I will see if I can compile the latest version with that commit in you linked to - fingers crossed!

Thanks again for all your help!

/Matt

from powerline.

No problem. Let me know if you still experience the issue after updating iTerm2 and I'll reopen the issue.

from powerline.

For any who experience the same problem the issue was resolved via updating iTerm to the latest nightly build which can be found at:

http://iterm2.com/nightly/latest

Huge thanks to @Lokaltog for all the help and a great tool

/Matt

from powerline.