Skip to content
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

Closed
3 tasks done
Goku-San opened this issue Oct 19, 2022 · 10 comments · Fixed by #977
Closed
3 tasks done

Fira Code Nerd Font Mono is not displaying == sign correctly #975

Goku-San opened this issue Oct 19, 2022 · 10 comments · Fixed by #977

Comments

@Goku-San
Copy link

🗹 Requirements

  • I have searched the issues for my issue and found nothing related and/or helpful
  • I have searched the FAQ for help
  • I have searched the Wiki for help

🎯 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)?

  • 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_correct

st call inside config.h
static char *font = "FiraCode Nerd Font:style=Medium:size=12:antialias=true:autohint=true";

st_incorrect

st call inside config.h
static char *font = "FiraCode Nerd Font Mono:style=Medium:size=12:antialias=true:autohint=true";

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

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?

@Goku-San
Copy link
Author

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.
I checked the reported signs from #973 and #934, only the equal sign == is not working.

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

Can see it 👍 or :-(

image

This is definitively the same issue, broken ligature. Let see

@Goku-San
Copy link
Author

Nope can't see it... 🙁

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

"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?

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

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.

@Goku-San
Copy link
Author

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...

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

Ah yes...

Here the history of font updates:

$ git log --pretty=format:"%h %ad -- %s by %an" src/unpatched-fonts/FiraCode/Medium/FiraCode-Medium.ttf
78be0e1e7 Tue Dec 7 12:14:51 2021 +1300 -- Add unpatched FiraCode v6.2 by Sean Fausett
d23d0e008 Sat Dec 4 14:36:29 2021 +1300 -- Add unpatched FiraCode v6.1 by Sean Fausett
dea135924 Mon Apr 27 21:31:40 2020 +0200 -- Add unpatched FiraCode v3.1 files by Oliver Hoffmann
2d32a1f44 Sat Jan 18 16:08:10 2020 -0800 -- Updates Fira Code source to v2.0 (#424) by Ryan L McIntyre
dfc31db1d Mon Sep 9 20:27:00 2019 +0200 -- Update unpatched Fira Code fonts to 2.0 by Hugo van Rijswijk
d9ea69ac6 Thu Oct 4 16:21:01 2018 +0200 -- updated FiraCode to version 1.206 by mashehu
ad162ace7 Sat Mar 10 17:39:23 2018 -0500 -- Adds sources for 'ttf' format of FiraCode (WIP #244) by Ryan L McIntyre

But the ligature removal table has never been updated along with it

$ git log --pretty=format:"%h %ad -- %s by %an" src/unpatched-fonts/FiraCode/config.json
a2f56206e Sun Feb 25 15:18:48 2018 -0500 -- Adds new config files (WIP #186) by Ryan L McIntyre

😬

@Finii
Copy link
Collaborator

Finii commented Oct 19, 2022

Thanks for your hard work...

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.

@Finii Finii mentioned this issue Oct 20, 2022
Finii added a commit that referenced this issue Oct 20, 2022
[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>
@Finii Finii mentioned this issue Oct 20, 2022
2 tasks
Finii added a commit that referenced this issue Oct 20, 2022
[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>
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 24, 2023
LNKLEO pushed a commit to LNKLEO/Nerd that referenced this issue Nov 24, 2023
[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>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants