Unable to Get Working on iTerm2 about powerline HOT 9 CLOSED

same problem here (iTerm2 Build 1.0.0.20121224 with Vim 7.3p754 on OS X 10.8.2).

from powerline.

It wouldn't surprise me if this is the same issue as with rxvt-unicode. rxvt-unicode hijacks the entire Unicode Private Use Area for some other purpose, and replaces any glyphs from the PUA with the "undefined glyph". With rxvt-unicode you can avoid the issue by compiling it with --enable-unicode3, but I'm not sure what causes this to happen in iTerm or how it can be resolved.

The only tip I have for now is to use a font patched with the legacy font patcher (the legacy font patcher uses different but invalid Unicode code points which are compatible out-of-the-box with iTerm2 and rxvt-unicode), and changing the glyphs in your user configuration file. Check out the docs for instructions on how to edit your user configuration.

from powerline.

I am also having this issue, and using and old patcher/glyphs resolved this. After patching your font you can copy/paste the glyphs from here and here to your config.json and vim theme files.

What was the reason for changing the reference to the glyphs?

from powerline.

This problem is fixed in gnachman/iTerm2@8e3ad6d.

Thanks to @gnachman!

from powerline.

@liamcurry Several font gurus have complained that we shouldn't use existing unicode areas with unassigned glyphs because they may be assigned to something else in the future, and that the private use area should be used for all non-standard/application-specific stuff. Also this caused rendering issues in some use cases because the previous glyphs were registered as non-printable if I remember correctly.

from powerline.

@Lokaltog makes sense. Compiling/installing iTerm2 from the git repo did fix this issue for me (thanks for the suggestion @qqshfox)

from powerline.

A quick note about the iTerm2 fix.

While I can see it in the commit log of the latest release, something else in that release introduced the issue again. This has been confirmed by a couple more users with the latest iTerm stable release (v1.0.0.20130210) - See gnachman/iTerm2@8e3ad6d#commitcomment-2475692.

I haven't had the chance to dig through the source and see what caused all of that but I can confirm that today's nightly build has that fixed (and so far being quite stable) - Obviously, compiling from source (master branch) works too.

Hope that saves someone some unnecessary tinkering time.

from powerline.

So this is happening again.

from powerline.

@rhoml Can you file a bug here with details?
https://code.google.com/p/iterm2/issues/list

from powerline.