-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
(Not Bug) How to make the width of " "(space) consistent with other font glyphs when toggle fake bold. #12234
Comments
Sorry, could you help clear one thing up? By
Do you mean something like #10678, where the "bold" text ends up getting cut off? |
Yes, you are right. I am sorry to my ambiguous description. Fortunately, you are so professional to understand it. Besides, my neovim behavior is just like https://github.com/microsoft/terminal/issues/9381#issuecomment-1004445152 after changing the value of fontweight as "bold" in settings.json. |
No worries, I see a bunch of these every week so you learn to read between the lines 😅 I'm gonna mark this as a /duplicate of #10678 for tracking purposes. Thanks for confirming! |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
My favorite monospace font is published wih only the "Light" fontweight. Therefore, i set the value of fontweight as "bold" in settings.json to get more attractive display performance. However, it active the fake bold function, the width of characters are stretched to larger except the " "(space). The inconsistency between these characters disturb my neovim display. As far as i know, the directwrite(direct2d) based text render engine is responsible for the phenomenon. I suppose that stretch the width of " "(space) will solve this problem. Would you mind tell me how can i do that. Thanks for your patience and kindness.
The text was updated successfully, but these errors were encountered: