-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patched symbols not showing #57
Comments
Did you copy These are the lines you should uncomment.
|
Ok, that was embarrassing: The lines you posted were commented out in my Thanks for fixing this so quickly (seriously, that was impressive!). I'm looking forward to using this beautiful tool for a long time :) |
No problem They indeed are commente by default, and users have to uncomment them if they have proper fonts installed. This is soon going to be the case for Emoji like symbols because with the transition to Unicode 9, programs don't agree on characters' width which is causing breakage. |
Oh, ok that makes sense then. Anyway, I'll fight my way through the config now to see what else is there to explore. I have to say it is quite magnificent that you managed to get all of this in such little space without the necessity of installing something. Good work! |
I'm aware this is an annoying and perhaps minor issue, but I've been googling for multiple hours now without a solution.
Here is what's wrong: The symbols, that if I understood correctly are introduced when patching a font, are not displaying for me. Others, however, work without problem, such as the battery symbol. Please have a look at the screenshot to see what I mean.
https://s9.postimg.org/ki2d54szz/powerline_issue.png
I checked font settings and encoding settings (UTF-8) in iTerm2 (which I'm mainly using). I also tried different patched fonts, including Source Code and Meslo, both show the same behavior. I checked locale, which for some reason is empty but I haven't been able to define it permanently. Don't know if that's important. I'm sure I've tried other things but forgot about it since they also didn't fix the problem.
Any what it could be or how to narrow the source down? I didn't run into this issue with the tmux-powerline repository maintained by erikw, which is why I suspect it's the config, but I don't know enough about it to be sure.
The text was updated successfully, but these errors were encountered: