Package Details: nerd-fonts-complete 2.0.0-5

Git Clone URL: (read-only)
Package Base: nerd-fonts-complete
Description: Iconic font aggregator, collection, and patcher. 40+ patched fonts, over 3,600 glyph/icons, includes popular collections such as Font Awesome & fonts such as Hack
Upstream URL:
Keywords: font fonts nerd nerd-fonts nerdfonts otf ttf
Licenses: MIT
Conflicts: nerd-fonts-complete-mono-glyphs, nerd-fonts-git
Submitter: SuperBo
Maintainer: glider (devopsdeluxe)
Last Packager: devopsdeluxe
Votes: 107
Popularity: 9.464480
First Submitted: 2016-08-21 07:32
Last Updated: 2018-06-04 15:14

Required by (9)

Sources (14)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

Francky_TuxnVape commented on 2017-09-12 17:38

I saw a default in the version 1.1.0-3 of the package nerd-font-complete. In fact the icons like the house for home are very small than before the up date. So I was forced to use a font named "Inconsolata Nerd Font Medium" in my case. (zsh shell)

denlillemand commented on 2017-08-23 07:18

Argh okay @glider, thanks for the quick response ... It was the knack font i was looking for, i didn't know the name of the hack font was changed in the package.


glider commented on 2017-08-22 17:54

Hi @denlillemand,
I think the nerd-fonts package only contains the patched-fonts Hack that is named "Knack".
- This is the "Knack" font:
- And this is the original Hack font:

If you want to use the original Hack font, you should install the package "ttf-hack" in the extra repo instead.


denlillemand commented on 2017-08-22 13:12

Hi, i installed this package, but the Hack font is nowhere to be found after the installation. I haven't checked the rest of the fonts, but some does work fine.
Do you know why this could be?


midgard commented on 2017-08-13 13:51

[Package etiquette] Hi, you should quote variables that may contain spaces, in particular ${pkgdir} and ${srcdir} on lines 90-92.

In fonts_dir (assigned on line 22) you should account for the possibility that nerdfonts_dir can contain a quote. Suggested solution:
This uses single quotes instead of doubles and replaces all ' in nerdfonts_dir with '\''.

Prefix variables you introduce with _ or make them local (e.g. «local extension="otf"» instead of «extension="otf"»).

Thanks for packaging for the AUR (love this package) and have a nice day.

ryanoasis commented on 2017-05-09 00:51

@SuperBo Thank you for this package. Great work :) I also agree that it makes sense to split the variants into separate packages so totally on-board with that idea :)

Just to clarify for anyone the root cause of the issue is that there is no internal font name difference between the mono and non-mono variants.

Thanks to @jayywolff for mentioning the issue, you can see my comment as well here:

This root cause issue should be fixed in v1.1 or maybe slip to a different future release.


SuperBo commented on 2017-05-06 07:03

@jayywolff: Thanks for the idea. I now split into two variants, non-mono-glyph(this package) and mono-glyph.
@Light2Yellow,@chrko, @diyod: If you got the problem with current version, please try this package:

Sorry for this inconvenient.

Anonymous comment on 2017-05-05 21:23

Well, for me the glyphs are now broken:
The font's name is "FuraMonoForPowerline Nerd Font" and the theme is powerlevel9k.
The glyghs were rendering perfectly before the update. Can I preserve the old behaviour?

UPD. sorry, missed the second part of your comment. Hope it'll get fixed soon, thanks.

jayywolff commented on 2017-05-05 14:37


The upgrade 1.0.0-2 -> 1.0.0-3, Removing "single-width-glyphs" so the system would use the non-single-width-glyphs fixed a bug with small glyphs I've been dealing with for months now. Thank you! However since some people are complaining, it might make sense to maintain a "single-width-glyphs" and "non-single-width-glyphs" variant of nerd-fonts-complete. That way everyone can choose which version works best for them.

Of course, the upgrade also screwed up the alignment of the powerline symbols but thats always a mission to line up properly, I'll figure out a workaround there.

I had been following this bug report upstream for a while, but didn't realize it was just due to the way it was packaged. I'll report my findings there too.

chrko commented on 2017-05-05 12:36


The upgrade 1.0.0-2 -> 1.0.0-3 broke my fonts, too -.-