Package Details: ttf-iosevka-custom-git 1668963274-1

Git Clone URL: (read-only, click to copy)
Package Base: ttf-iosevka-custom-git
Description: A slender monospace sans-serif and slab-serif typeface inspired by Pragmata Pro, M+ and PF DIN Mono.
Upstream URL:
Licenses: custom:OFL
Conflicts: ttf-iosevka-custom
Provides: ttf-iosevka-custom
Submitter: andykluger
Maintainer: andykluger
Last Packager: andykluger
Votes: 3
Popularity: 0.000000
First Submitted: 2017-02-07 06:42 (UTC)
Last Updated: 2022-11-21 17:54 (UTC)

Latest Comments

1 2 3 Next › Last »

RealOrRandom commented on 2022-11-21 12:31 (UTC)

The master branch has been renamed to main. This needs to be fixed in the PKGBUILD.

andykluger commented on 2021-06-14 20:14 (UTC)

Anyone have thoughts on replacing these packages with TTC/Super-TTC builds?

Please see "Packaging Format" at and let me know what you think!

andykluger commented on 2020-11-10 03:46 (UTC)

I configured a GitHub workflow/action as a build server for this.

Please have a look and message here or submit an issue for any assistance/complaints.

andykluger commented on 2020-03-05 21:39 (UTC)

Heads up everyone!

Looks like the naming of these build variants is changing upstream, so the relevant package names here will change accordingly as well.

  • Iosevka (custom) will now have wide arrows and geometric symbols
  • formerly "termlig" -> "term"
  • formerly "term" -> "fixed"

I will be requesting deletion of the termlig package for the rename. I will be requesting deletion of the slab packages because no one uses them.

Please stay tuned for updated packages as I ensure a successful transition.

andykluger commented on 2020-02-03 17:36 (UTC) (edited on 2020-03-13 05:15 (UTC) by andykluger)

I've now included, disabled unless manually uncommented, a patch to get back the old, smoother, "toothless" capital G, as seen here (look for "LIGHT"):

If anyone else here prefers that toothless version, please express that at so that it might return upstream as a glyph variant option.

andykluger commented on 2020-02-03 15:48 (UTC)

@E I've changed things so that the file is no longer overwritten, so there shouldn't be any trouble with checksums anymore. Note that this build does not check for the user-defined toml file in the build directory, but in ~/.config/iosevka/

Let me know if this is good for you.

andykluger commented on 2020-01-26 00:05 (UTC)

@E You can always check out the committed version of that file, or tell yay to check it out again.

I'll remove the integrity check if a second person requests it

Epdfjasfvzp commented on 2020-01-25 23:38 (UTC)

@andykluger It's because I use yay, perhaps I'm the only yay user of this package. I think it would be better not to check since I doubt there are any security implications for that.

andykluger commented on 2020-01-25 04:11 (UTC)

@E it sounds like you are first overwriting that file yourself. It will work if instead you keep your custom file in the mentioned folder, and run makepkg from the clean, checked-out state of this repo.

However, if everyone still wants me to stop checking the integrity of this repo's file, I will.

Epdfjasfvzp commented on 2020-01-25 03:47 (UTC)

But after the hash check, it will overwrite the shipped copy with one from ~/.config/iosevka/ if it exists.

For me I can't install it without editing the PKGBUILD because it will complain that my private-build-plans.toml fails validation.