Package Details: ttf-iosevka-custom-git 1702712905-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: 2023-12-16 22:26 (UTC)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

andykluger commented on 2023-12-04 20:07 (UTC) (edited on 2023-12-04 20:07 (UTC) by andykluger)

@RealOrRandom @everyone

I'm not sure myself if it makes sense to keep these packages here in the AUR, since I use the GitHub Actions flow for my own builds.

So please, anyone, let me know -- should I:

  • a) remove my ttf-iosevka-*custom-git packages from the AUR?
  • b) remove those AND the ttf-iosevka-git package?
  • c) keep maintaining them here?
  • d) keep maintaining them AND add a quasi proportional PKGBUILD (which is already getting generated)?
  • e) something else?

andykluger commented on 2023-12-04 20:02 (UTC)


These PKGBUILDs are generated from that repo (I will update them here soon when Iosevka v28 is released with some new names/paths).

For a local QP build on Arch, I suggest you clone that repo and use it to generate all its PKGBUILDs (which include one for ttf-iosevka-quasi-proportional-custom-git). You'll have to decide if you prefer to configure it via my vars.nt or your own ~/.config/iosevka/private-build-plans.toml, but then it should just be:

$ ./mk/
$ cd pkgs/ttf-iosevka-quasi-proportional-custom-git
$ makepkg -sci

Just note, especially if using your own private-build-plans.toml, that the repo is currently configured to pull iosevka from the dev branch, which has all the new names for everything.

RealOrRandom commented on 2023-12-04 14:52 (UTC)

@andykluger Are these AUR packages still the way to go, or do you recommend switching to

Background: I'd like to build a custom quasi-proportional variant, and there's no AUR package for this here. But I think I'd be happy with a local build, I won't need GitHub Actions...

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