Skip to content
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 symbols in airline plugin #41

Closed
anuvyklack opened this issue Aug 1, 2019 · 8 comments
Closed

Powerline symbols in airline plugin #41

anuvyklack opened this issue Aug 1, 2019 · 8 comments

Comments

@anuvyklack
Copy link

image

Aversom app, thank you!
But there is an issue on Windows 10 1903. Powerline symbols are visible, but showing not correct, as is shown in the screenshot.

@yatli
Copy link
Owner

yatli commented Aug 2, 2019

most likely a configuration issue -- try altering termguicolors?

@yatli
Copy link
Owner

yatli commented Aug 2, 2019

Also, I can see some alignment problems -- I have put a lot of time on this but still, without proper upstream support I'm kind of doing it blind.

Are you running the latest release? It may help with the alignment

@yatli
Copy link
Owner

yatli commented Aug 2, 2019

btw if you turn of FVimAutoSnap you'll have floats :)

@anuvyklack
Copy link
Author

image

Set termguicolors helped, thank you!
Right now I'm using version 0.2-46, and in it appears another problem: letters are trimmed from below, as shown in the screenshot.

@yatli
Copy link
Owner

yatli commented Aug 8, 2019

@anuvyklack thanks for reporting! I've changed the pixel snapping rule in patch 46 but apparently it worked less well for other fonts and DPI settings.
Will try to figure out with your setting. :)

@yatli
Copy link
Owner

yatli commented Aug 8, 2019

font rendering issue should be resolved now

@anuvyklack
Copy link
Author

image

Yes, font rendering issue has gone. Also, nerd font symbols alignment is much better now.

@yatli
Copy link
Owner

yatli commented Aug 9, 2019

There's still some horizontal alignment problems -- see the airline <| 22% part.
I think we can close this issue for now -- I will improve the font rendering once the upstream (Avalonia) changes are merged.

@yatli yatli closed this as completed Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants