-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Powerline support in 0.6 #44
Comments
I'm using Konsole (at least, it is Konsole on the screenshot). |
Looks like there’s no easy way to fix it. Powerline is a hack, so expect it to behave like a hack. Related: powerline/fonts#31
|
Powerline itself, as idea, yes, a hacky thing. So, TL;DR: Powerline can brake things when autopatched, but it is possible to just add few symbols of specified look directly into the font (like it done in PragmataPro). Although, yes, it will take few hours or so to do that (in case of FontForge and ttf fonts. And, talking on Fira* — I, actually, have no idea how to edit it under GNU. |
The problem is with triangles only. Fonts in general are not well suited On Tue, Feb 23, 2016 at 2:15 AM Vadim A. Misbakh-Soloviov <
|
Cache if gem is indexed in Gemstash::Storage
Hi there!
You've announced Powerline support in the 0.6 version, but it seems, they've added a bit buggy:
Also, I've noticed a little offset to the right side for ± symbol (and bottom part of + seems like cutted), and, somewhy, coloured circles (at the right side, which, actually, using same symbol in all three cases) has some positional offsets (yellow one looks like a bit divided at the left side, and red one looks smaller than yellow). I think, that is somehow related to not-really-monospaced nature of the ligatures for that symbols in the font. Maybe, due to some bug during powerline-patching, or so. How do you think?
The text was updated successfully, but these errors were encountered: