-
-
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
Better power/airline alignment in iTerm2? #131
Comments
Looks like no, no easy way to fix it. Powerline is a hack, so expect it to behave like a hack Related: powerline/fonts#31
|
Hack has a long thread of correcting the arrow bit by bit. Reference: source-foundry/Hack#33 Whereas Fantasque Sans Mono has perfectly aligned arrow: If Fira Code can do the same, that would be really awesome! |
True, but that doesn't mean there is no way we can't make it so the at least it is adjustable to look as close as aligned properly as close as possible. FiraCode right now doesn't seems to be able to can't make it look at least ok (without gap or able to align it close to the center) even by adjusting the spacing. Fantasque font works fine almost out of box on iTerm2 though. I also noticed that PragmataPro with powerline patch looks pretty good on Terminal.app out of box, it look fine after minor spacing adjustment on iTerm2. Perhaps you should look into PragmataPro and see how they made it so it look good on both iterm2 and terminal |
And btw, here is another font that the arrow looks aligned on both terminal.app and iterm out of box. |
…endpoint Support the latest_specs endpoint
I started using vim-airline recently and after tinkering with the vertical alignment and sizes with the font I finally got the
>
block on the left aligned pretty well but the<
block on the right is not aligned as wanted.Here's a picture of the issue

Is there any way to fix this? To achieve this I had to set my ASCII font to Fira Code Retina size 11, my non-ascii font to Fira Code Retina size 13 and adjust the vertical alignment to about 1.15:
The text was updated successfully, but these errors were encountered: