-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[v0.10] When two characters are ligatured, the first one becomes invisible #4974
Comments
What font size are you using? What version of Terminal? |
Default size i.e. 12.
Windows Terminal (Preview) |
I am also having this issue, using 10pt Fira Code, no matter the zoom level, I just built from commit c0d704e Here you can see the //, :: and www ligatures drawing incorrectly: |
We thought we'd fixed this with #4806, but perhaps we didn't. |
do you have an ETA for this issue @DHowett-MSFT ? |
Unfortunately, I do not. Sorry. |
By the way, I tried switching my font to Cascadia instead of Fira Code and this issue does not occur with Cascadia. |
I'm using WT Version 0.10.781.0 and I can not seem to reproduce it. I'm also a Fira Code lover myself. |
I'm on WT 0.10.781.0 and do reproduce this bug with Fira Code. |
I'd bet this might have to do with not only the font face, but also the font size and display resolution. @FallenGameR (or anyone else reproing this), could you also make sure to share your |
@zadjii-msft here are the settings that causes this issue:
Resolution: 1920 x 1080 |
Reproduced with Windows Terminal 0.10.781.0, Fira Code 1.206, display resolution 1920x1200, every font size from 6 to 14. Updating to Fira Code 2.000 fixed the issue and all ligatures show up correctly at all settings I'm able to test. |
Ah. That's probably it. I'm at 2560 x 1600. I can't find a way to reproduce it. |
The update to Fira Code 2.000 fixed the issue as well on my side |
Same. Updating to Fira Code v.2 fixed the issues on my side. |
If It can be of any help...this worked before #4806 |
Thanks! 4806 describes the same bug as this, so it definitely worked before 4806 ;) |
I thought I'd share my experience with this bug: I had an older version of the Firacode fonts hanging out in Windows 10 Version 1909 (OS Build 1836.752) |
Any ETA on this? |
@privacyguy123 Unfortunately not at this time. I tried reproing this Friday, but I couldn't get this to happen on my machine at all with Fira Code 1.2. Hopefully someone else on the team will have a better chance at reproing this. If we can't get a repro locally, we could try psychic debugging by looking at the changelog of what Fira Code changed on their side between 1.2 and 2.0. Maybe that would point us in the right direction of something we've done wrong. It's also just possible that some of the rendering changes that are baking for 0.11 (#778/#5185) might just fix this, which might explain why I couldn't get a repro. |
@zadjii-msft / @DHowett-MSFT : the bot can't complain about issue titles, but can you please fix |
@jsoref done |
Technically, I suppose, I should say "it doesn't". It probably could. |
Come on boys - new release and this was overlooked? It worked fine in earlier versions ... Here is the f00king exact font it's happening with on my machine ;) |
So no, this hasn't really bubbled up in our own priority list. Also, at least I was hoping that #5345 would just magically fix this (as there was quite a bit of renderer changes in that PR). EDIT: Even with the repro, I'm pretty sure this isn't going to make the 1.0 cut for the aforementioned reasons. If someone in the community were generous enough to contribute a fix, we'd probably take that though! |
EDIT: Bug fixed by repatching my own Fira Code 1.2 with https://github.com/ryanoasis/nerd-fonts font-patcher script fixes this bug, perhaps the one they have uploaded is broken? 🤪 |
This bug occurred on my machine with FiraCode 4.0. The problem was resolved when I unblocked the FiraCode ttf files before installing them and restarted my terminal. |
I'm curious if this just went away in 1.16. The Atlas engine might have just fixed this. |
Anyone still seeing this on Terminal 1.18/? There's been a whole pile of massive renderer rewrites in the last year. |
Environment
Steps to reproduce
--
.Expected behavior
The first
-
shouldn't disappear.Actual behavior
The first
-
is disappeared.The text was updated successfully, but these errors were encountered: