-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Fira Code Nerd Font Mono is not displaying == sign correctly #975
Comments
Thank you for reporting the issue! This reminds me of #973 Wondering why this shows all up now, was I am not aware of any related changes. The one working was also directly from master ~9 days ago? |
The working was from master and according to the https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraCode its from ~9 days ago. I can only confirm for Fira Code because I only use them. I install them manually. I check every weekend for updates. |
Nope can't see it... 🙁 |
"Lets see" means ... wait, I start searching for the reason :) The commit is question in 5d218b1 There I fixed the ligature removal code. Before the commit the code ... did not do much. Afterwards it removed all the tables it was intended to remove. But obviously the ligature removal data is outdated. It never showed because the ligature removal never happened because it was broken. ... I guess we should just remove ligature-removal (as it never worked anyhow, at least not in the more recent past). Do you want or not want ligatures? |
And then the next question (because here is night and I have to sleep soon): I was working in the Seti Icons update and am almost finished. Shall we wait with a bugfix (for the == bug) until Seti update is ready? That will be only in 24h or something. |
First question ---> I want ligatures Second question --> Yes, no problem I can wait.... You have I good night rest... we are in the same time zone :) Thanks for your hard work... |
Ah yes... Here the history of font updates:
But the ligature removal table has never been updated along with it
😬 |
You are welcome :-) The solution is simple and the same as in the Hasklug Issue. Will change that along with the Seti update, like, tomorrow. |
[why] Keeping the ligature removal tables up to date with source font updates is quite a maintenance burden. Usually if a terminal supports ligatures at all it has an option to disable them. Present ligatures do not prevent monospaced fonts and monospaced detection. It was only present in v2.0.0, and the code has been broken with v2.1.0. [note] Updated example ligature removal table to the one for Iosevka. Left stubs in relevant code passages to facilitate finding this commit. Fixes: #976 Fixes: #975 Fixes: #973 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why] Keeping the ligature removal tables up to date with source font updates is quite a maintenance burden. Usually if a terminal supports ligatures at all it has an option to disable them. Present ligatures do not prevent monospaced fonts and monospaced detection. It was only present in v2.0.0, and the code has been broken with v2.1.0. [note] Updated example ligature removal table to the one for Iosevka. Left stubs in relevant code passages to facilitate finding this commit. Fixes: #976 Fixes: #975 Fixes: #973 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
[why] Keeping the ligature removal tables up to date with source font updates is quite a maintenance burden. Usually if a terminal supports ligatures at all it has an option to disable them. Present ligatures do not prevent monospaced fonts and monospaced detection. It was only present in v2.0.0, and the code has been broken with v2.1.0. [note] Updated example ligature removal table to the one for Iosevka. Left stubs in relevant code passages to facilitate finding this commit. Fixes: ryanoasis#976 Fixes: ryanoasis#975 Fixes: ryanoasis#973 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
🗹 Requirements
🎯 Subject of the issue
Experienced behavior:
== sign not displaying properly with FiraCode Nerd Font Mono Medium. Few days ago ( Saturday or Sunday ) I updated the Fira Code Nerd Font. Before that everything was displaying correctly.
Expected behavior:
Expect to display properly as with original Fira Code Medium or FiraCode Nerd Font Medium.
If I use FiraCode Nerd Font Medium or Fira Code Medium than icons in vim are clipped.
So if you can please fix the == sign or revert to the patch from 9 days ago, when all was good.
Example symbols:
🔧 Your Setup
Which font are you using (e.g.
Anonymice Powerline Nerd Font Complete.ttf
)?Please give the full filename
Fira Code Medium Nerd Font Complete Mono.ttf
Where did you get the file from (download link, self patched, source downloaded from link...)
https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraCode
Which terminal emulator are you using (e.g.
iterm2
,urxvt
,gnome
,konsole
)?st terminal with ligatures patch
Are you using OS X, Linux or Windows? And which specific version or distribution?
Linux - Manjaro XFCE
★ Screenshots (Optional)
st call inside config.h
static char *font = "FiraCode Nerd Font:style=Medium:size=12:antialias=true:autohint=true";
st call inside config.h
static char *font = "FiraCode Nerd Font Mono:style=Medium:size=12:antialias=true:autohint=true";
The text was updated successfully, but these errors were encountered: