Sourcecode Pro Powerline with tmux split causes a column misalignment

[linu...@gmail.com]

Screenshots attached below:

You can see it on the VIM status lines...

Here's a copy/paste from tmux of the status lines, but not sure if it'll be useful...

NORMAL  +0 ~0 -0   ~/7g-backend/backend/atg.py                                                                      pollATG  python  utf-8[unix]   91% ☰ 1248/1364  :105 
  2 /srv/fieldagent/7g-backend/backend/atg.py|830 col 5| C901 'ATG.parseResponse' is too complex (66)
~
~
~
~
 [:flake8 "/srv/fieldagent/7g-backend/backend/atg.py"] [Quickfix List] [-]                                                                        [unix]  100% ☰    2/2  : 22

[Mike Frysinger]

the Powerline font is not a monospace font.  if they claim to be, they're lying ;).

https://crbug.com/737454 is tracking the issue in general to workaround broken fonts.

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/f4b587c2-fecf-4eeb-a0e1-5dfb1f94f358%40chromium.org.

[linu...@gmail.com]

I opened an issue here too...

https://bugs.chromium.org/p/chromium/issues/detail?id=852491

Thanks, can anyone else reproduce this?

[linu...@gmail.com]

Cool, thanks!

[linu...@gmail.com]

However...

I use the same font on a Linux machine, with xfce4-terminal, and/or alacritty, etc... and do not have this issue with the font.

It's not quite fair to blame the font when it works elsewhere.

[linu...@gmail.com]

Actually...

This happens with vim-airline, without powerline fonts enabled.

Just vanilla vim airline in a tmux split causes this behavior.

[Mike Frysinger]

it's hard to guess based on a picture.  really  would want to see the actual text content.  it seems like your initial copy & paste was corrupted and didn't preserve the UTF8 content.  or it did and you're using PUA codepoints.

here's snippets from your original e-mail content:

NORMAL =EE=82=B0

=EE=82=B0 ~/7g-backend/backend/atg.py

=EE=82=B2 pollATG

=EE=82=B3 python

=EE=82=B2 utf-8[unix]

=EE=82=B2  91%

=E2=98=B0 1248/1364

=EE=82=A1 :105

=EE=82=B2

=EE=82=B2=EE=82=B2 [unix]

=EE=82=B2 100%

=E2=98=B0    2/2

=EE=82=A1 : 22

=EE=82=B0 is U+E0B0 which is in the PUA (U+E000 through U+F8FF)

same goes for all those codepoints that start with =EE=82.

according to Unicode, those should all take up one column.  they do in hterm.

=EE=98=B0 is U+2630 which is ☰ which should only take up one column.  it does in hterm.

looks like the powerline font (going by Source Code Pro for Powerline.otf, although you didn't say which one you were using), it defines glyphs in the PUA.

U+E0A0 is the line+up arrow

U+E0A1 is the LN symbol

U+E0A2 is a padlock

U+E0B0 ... U+E0B3 are the right/left arrow heads

you should figure out which one of those glyphs is causing misalignment and see what is miscounting it.

-mike

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/c373f7c1-cb01-4fec-b471-f38b67e28fef%40chromium.org.

[linu...@gmail.com]

You can just grab some glyphs from vim-airline to see for yourself:

https://github.com/vim-airline/vim-airline/blob/master/doc/airline.txt#L258


And here you can see what each is doing: 

With powerline font:



Without powerline font: