-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
bug: Nerd fonts will probably not be usable anymore after nixpkgs 25.11 #6160
Comments
Not really sure if this is what you're asking for, but since they moved the Nerd Fonts to a new package, I recently had to update my
I'm surprised Footnotes |
Thanks, @poopsicles! Running |
Looked around and found #520, which linked to #682 which added in this file: home-manager/modules/misc/fontconfig.nix Lines 108 to 113 in 8632735
So it does refresh the cache, but with
I'm not sure if that needs to be switched to But anyways, tl;dr is to force the cache to actually get cleared first if any font problems occur (though that's probably unlikely...in this case the folder structure of the fonts was changed). |
Hello @poopsicles, Thanks for your fix!
Yes, this one was already done.
This is what was missing 🙂. My assumption was that home-manager was already doing this, but seems it is not, good catch 👍. Looking back at #682, it is in fact: ${getBin pkgs.fontconfig}/bin/fc-cache -f Perhaps @rycee has more insight on this matter. |
Are you following the right branch?
Is there an existing issue for this?
Issue description
Hello,
I am using home-manager with nixpkgs in a flake, both on master.
Lately a modification occurred on nixpkgs on how the nerdfonts are packaged (see NixOS/nixpkgs@de4dbc5).
Since this modification, alacritty seems unable to load the fonts.
Following are my findings while looking at the issue.
Here are the Alacritty logs:
The font path used by alacritty is the one listed by
fc-list
:But the path is obviously not the right one:
The fonts are in fact located here:
If anyone has an idea of how to fix/workaround this, I will be happy to try 🙂.
Maintainer CC
@rycee
System information
The text was updated successfully, but these errors were encountered: