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

“Look ma’, it’s animated!” — or why do my dashes move under the cursor? #107

Closed
alerque opened this issue Sep 17, 2015 · 6 comments

Comments

@alerque
Copy link
Member

alerque commented Sep 17, 2015

So here's one for you (OTF, Font version 2.013, Linux, FT 2.6, Termite VTE3-ng based terminal):

selection_058

Note the two dashes as part of the GNU flavored long option syntax are at different heights. Both are the same font, size etc. But when the (block) cursor passes over it it reverses the foreground color and changes the background. At first I though this was screwing with the anti aliasing and making it appear to move, but it turns out it's switching to italics. This is a subtle change for most letters but when it's a dash and the glyph jumps up and down it's rather jarring.

I can see why italics might render at a different height, but given that this is a source code font I think the dashes need to stay at the same height.

Also notable, the bold variant seems to be the same as the italic an the cursor doesn't produce any motion when going over bolded dashes.

@chrissimpkins
Copy link
Member

Interesting. There are a few other issue reports about one pixel offsets between sets. To date, these have been between the regular and bold sets. Let me look at the actual position of the glyphs in the regular and italic sets to see if it is positioned at a different vertical level.

@chrissimpkins
Copy link
Member

You win the issue report title of the year award by the way...

@alphapapa
Copy link

Definitely LWN-worthy. :D

@chrissimpkins
Copy link
Member

Identified the problem. Will try to work a fix in to the upcoming release.

@chrissimpkins
Copy link
Member

Fixed this today. Will be included in the next release.

@chrissimpkins
Copy link
Member

Fixed in v2.015 release. Available now. Will close this issue. Feel free to reopen if you have any problems with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants