[bug] vertical lines render in a jagged (not perfectly) vertical zig-zag (only in tmux?)

[Jonathan Zacsh]

attaching screenshot of actual and expected behavior. I've only seen this on chromium-hterm.

The screenshot shows the center of my screen in a vertical "split" in tmux. Specifically, in the actual_vertical-line.png on lines 20,21 (of the vim session to the right side of the screen) have green pipe characters that are further to the right than identical green

As much info as I can think of:

• my chromebook version: 36.0.1985.126 (Official Build 283281)
  
• my tmux version: 1.8 (tmux -V)
• my hterm version: 0.8.27
• inside tmux, I have env output with: TERM=xterm; COLORTERM=rxvt-xpm
• outside tmux, I have env output with: TERM=xterm
  
• i always use hterm in fullscreen (open an ssh session, then hit the chromebook keyboard's fullscreen key)
• worth noting both screenshots were taken with the same session in hterm...
• I can actively flip back and forth between one tmux-window displaying the bug, and another displaying the expected behavior, and not cause a change in either.

[Robert Ginda]

You're probably displaying some Unicode characters that don't match the width of the other characters in your fixed width font.

--
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/6670ee4b-9670-4130-8ff7-3327c46dfc46%40chromium.org.

[Jonathan Zacsh]

Brilliant! Thanks Robert.

Indeed, every funky character corresponds to one of my bash PS1 prompts to the left, containing: ┌┤

I suppose this never happens elsewhere because my only other machine is Ubuntu, where I use DroidSansMono...

Is there anyway to use my own custom font with hterm, or would the team be open to a patch to enable this?

ie, instead of:

term_.prefs_.set('font-family', 'Lucida Console')

be able to do this:

term_.prefs_.set('font-family', 'DroidSansMono')

term_.prefs_.set('font-family-src', "local('DroidSansMono'), url(http://fonts.gstatic.com/s/droidsansmono/v6/ns-m2xQYezAtqh7ai59hJYdJ2JT0J65PSe7wdxAnx_I.woff2) format('woff2'), url(http://fonts.gstatic.com/s/droidsansmono/v6/ns-m2xQYezAtqh7ai59hJUYuTAAIFFn5GTWtryCmBQ4.woff) format('woff')")

- see example CSS: http://fonts.googleapis.com/css?family=Droid+Sans+Mono

- general google fonts usage page: https://www.google.com/fonts#UsePlace:use/Collection:Droid+Sans+Mono

[Robert Ginda]

There is rudimentary support for web fonts in hterm already.  I'm getting on a plane so I can't get the link now, but you should be able to find it in the mailing list archive.

[Jonathan Zacsh]

ah, yes, you even posted with useful quickstart instructions: https://groups.google.com/a/chromium.org/d/msg/chromium-hterm/dFVAhCvaI4Q/G675nendpFAJ

term_.prefs_.set(

'user-css',

'http://fonts.googleapis.com/css?family=Droid+Sans+Mono');

// tried w/o ", monospace" to ensure it really works

term_.prefs_.set(

'font-family',

'"Droid Sans Mono", monospace');

However, I still see the unicode chars making a mess. On Monday, I'll check my desktop's terminal/settings/version/etc and try to see what's different...