Closed fr0zert closed 7 months ago
lhecker
commented
7 months ago Thanks for the feedback! This was recently fixed by #16729 which will ship in the next Windows Terminal version. We're still working on the fine details, but powerline glyphs will work for sure.
fr0zert
commented
5 months ago @lhecker ah it's been like two or three updates, and the problem's still there, even tried the pre-release version, it has this problem too. What's interesting is that when you answered me, I decided to try the pre-release version and it was already fixed there, but it looks like the problem is back (even though it never disappeared on release)
lhecker
commented
5 months ago When you say "pre-release version" are you referring to the preview version? #16729 wasn't released in preview yet. You need to use our nightly builds ("canary") instead. You can find the download links here: https://github.com/microsoft/terminal/discussions/16121 (I recommend the App Installer.)
fr0zert
commented
5 months ago oops, I apologize, I did get the url mixed up and was checking the wrong build 😬
Windows Terminal version
1.19.240130002
Windows build number
10.0.19044.0
Other Software
No response
Steps to reproduce
I use a custom prompt starship with default preset called Tokyo Night, with nerdfont called FiraCode(Mono)
Expected Behavior
No response
Actual Behavior
Custom prompt uses the semicircle symbol ""(\ue0b4) at the start of which, at certain zoom values(font size 11 for me), an extra pixel appears.
The problem appeared with the latest updates, since I have two versions of the terminal on the device, I can run them in parallel using all the same settings, and in the old version of such a problem is not observed.