-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Render private-use range unicode chars (except the four reserved by i…
…term). Some fonts use them for fancy special characters and it's nice to support that. The down side is that for normal fonts they'll render a bit uglier as a double-width character, but you shouldn't get them often anyway
- Loading branch information
Showing
3 changed files
with
24 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree with MindTooth.
the newest version of iterm2 on google code having trouble displaying the fancy character in powerline for vim now.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tried it in the current nightly, because the current release has it regressed as well, and the current nightly has also regressed. Alas.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it matters, I just tried compiling from master, it still fails rendering some characters (good example is vim-poweline for example)
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, here is screenshot of both side by side (the same special chars are used in all versions of powerline, vim, tmux, etc.)
The font used is the patched Menlo for Poweline. I was running the latest beta versions which were fine until recently, but few days ago or so they broke this font rendering.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is precisely how my issue looks as well, just to confirm.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you copy paste the actual characters in the status line in here? I guess I need a copy of the font as well to be able to reproduce this.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Powerline's documentation contains a list of glyphs used, as well as an explanation of the font patching process.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was recently a change that fixed a bug where the ASCII font was used for non-ASCII characters. Make sure you set both fonts to the powerline font and then this should work for you.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh yes, that does it! Thanks @gnachman
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have both fonts set to Deja Vu Sans Mono for Powerline and my glyphs don't display correctly (they match the failed screenshot above except instead of a square with an X mine are a square with a circle).
The characters are as follows:
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind, I was on an old version of powerline that still used the other glyphs.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After setting the non ASCII font, the problem is still not fixed. On iTerm2 nightly with Solarized dark and Meslo for powerline (on OS X 10.9), the color of the arrow is slightly darker.
![screen shot 2013-12-09 at 3 09 12 pm](https://camo.githubusercontent.com/8e1b992ae627988b26602f42abce7da204dc105b44b9a7b0379380644c07463d/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f3733393930332f313730353238382f38363061303133652d363064622d313165332d386561642d3862613133633762353639362e706e67)
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ettoredn, what should it look like? Can you provide a session log so I can try to reproduce?
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should look like https://gist.github.com/agnoster/3712874, more specifically: https://gist.github.com/agnoster/3712874/raw/5d28e2d9fe2e4d0a4fda0315ad97bdafa399425c/screenshot.png
Honestly I'm not so sure it's related to iTerm since I checked on Terminal and it shows a similar difference in colors. Anyway, in past versions it worked, as you can see from that screenshot.
To reproduce:
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind, I just realized it's related to window's transparency. Setting it to 100% opaque solved the "problem".
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The characters ± ➦ ✔ ✘ show up fine for me with Meslo LG S Regular and transparency. Weird.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, the characters are fine. Check this screenshot: what I was saying is that I was expecting also the |> character (sorry but copy+paste doesn't correctly copy the character) to appear as transparent as the rest. I'm not sure whether this is expected or not.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's working as intended: the background is translucent but the foreground is always opqaue.
8e3ad6d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use ettoredn step 4 , update font for non-ASCII characters and it works