Glyphs are cut off/truncated when using GPU/Metal rendering on a 1x display
Bug report
Thanks for filing an issue! Please answer the questions below so I can help you.
- iTerm2 version: Build 3.4.22
- OS version: 14.2 (23C64)
- Machine: MacBook Air (M1, 2020)
- Display: DELL S2722DGM (27-inch, 2560 × 1440)
- Attach
com.googlecode.iterm2.plist
here (drag-drop from finder into this window): com.googlecode.iterm2.plist - Attach a debug log, if possible: debuglog.txt
- When debug logging was enabled, I was using the Iosevka Uni font in a session, and I repeatedly toggled GPU rendering on and off.
- Attach a screen capture video if it would make the reproduction steps clearer.
PLEASE ATTACH YOUR PLIST FILE FOR BUG REPORTS! Seriously! I'll probably ask you for it if you don’t.
Detailed steps to reproduce the problem
- On a non-Retina/HiDPI ("1x") display, enable GPU rendering while using a monospace font with narrow and tall proportions (I have attached a font that I can reproduce the issue with).
- Observe that some glyphs are cut off.
What happened
Here is an animated example. When using the attached font (Iosevka Uni
) at 14 points, various glyphs are truncated horizontally, but only when GPU rendering is on, e.g.:
- The italic
d
inrudimentary
- The lower tip of the
t
infatih/vim-go
- Every
m
,u
, ande
- Every italic
"
,u
, anda
- etc…
Font used in the above GIF: IosevkaUni-12-18-2023.zip
The font provided is my bespoke custom build of Iosevka, a popular monospace font. The issue doesn't seem to occur on the SS03 variant (a preset that is provided upstream) for reasons I cannot discern. I haven't tested any other variants of the font. The issue also occurs with PragmataPro Mono, but I cannot upload it here because it's proprietary.
What should have happened
I expect glyphs to not be truncated horizontally like this, as it's a bit distracting. Still legible, but it could be better. I don't think this happens on Retina/HiDPI screens, as I don't remember this issue occurring at all on the built-in display. Whether the issue is still present (but effects negligible due to increased pixel density) on Retina or isolated to non-Retina I am not sure.