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

Git Clone URL: https://aur.archlinux.org/ttf-iosevka-custom-git.git (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: https://be5invis.github.io/Iosevka/
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)

Latest Comments

« First ‹ Previous 1 2 3

andykluger commented on 2018-10-10 20:55 (UTC)

@blueyed

I've enforced a shallow checkout now

andykluger commented on 2018-10-10 17:26 (UTC) (edited on 2018-10-10 17:29 (UTC) by andykluger)

@blueyed

  1. Yes, I think I'll update these to grab the master zip instead of a git checkout, thanks. I'm not sure how to properly get the revision info in that case, however.

  2. Look at the private-build-plans.toml -- the termlig-custom package builds according to the configuration under [buildPlans.iosevka-termlig-custom] . You can copy this file to ~/.config/iosevka/ to modify it, and the pkgbuild will use that.

blueyed commented on 2018-10-10 12:07 (UTC)

  1. Given the size of the repo it would be useful to have a ttf-iosevka-custom package for the latest release, and/or ttf-iosevka-custom-git using the master tarball instead.

  2. Do I understand it correctly that ttf-iosevka-termlig-custom-git is quite the same, but just defaults to building something else?

andykluger commented on 2018-08-22 00:27 (UTC)

@mustaqim (and everyone) it's now updated to use the new build system, but no longer looks at that environment variable. For configuration, please copy the provided toml file to ~/.config/iosevka/ and modify from there.

mustaqim commented on 2018-08-18 05:06 (UTC) (edited on 2018-08-18 05:10 (UTC) by mustaqim)

The build method has changed, you need to change edit this into the PKGBUILD:

prepare() {
  cd "Iosevka"
  sed -i '/# Building plans/a [buildPlans.iosevka-custom]\nfamily = "Iosevka Custom"\ndesign = ['"$IOSEVKA_DESIGN"']\n' build-plans.toml
}

build() {
  cd "Iosevka"
  npm install
  npm run build -- contents:iosevka-custom
}

This will add:

[buildPlans.iosevka-custom]
family = "Iosevka Custom"
design = ["v-y-curly", "v-l-tailed", "v-g-opendoublestorey", "v-zero-dotted", "v-asterisk-low", "v-dollar-open", "v-numbersign-slanted", "v-underscore-low"]

to build-plans.toml.

You also need to set an ENV variable that is comma separated(eg. in fish):

set -gx IOSEVKA_DESIGN '"v-y-curly", "v-g-opendoublestorey", "v-zero-dotted", "v-asterisk-low", "v-dollar-open", "v-numbersign-slanted"'

andykluger commented on 2017-05-12 16:35 (UTC)

@flying-sheep good idea, thanks, should work like that now.

flying-sheep commented on 2017-05-12 15:04 (UTC)

what you can do is checking for an env variable containing the settings. so people can do IOSEVKA_DESIGN='...' makepkg how about it?

andykluger commented on 2017-04-10 20:19 (UTC) (edited on 2017-04-10 20:24 (UTC) by andykluger)

@Eremiell It's meant to be a convenience for me, and a convenience for configuring your own custom builds. All the custom configuration is on line 25 of the PKGBUILD: make custom-config design='v-l-tailed v-i-hooky v-g-opendoublestorey v-m-shortleg v-zero-dotted' The character variant build options are listed and described (copied from upstream) in comments in the PKGBUILD. All character variants can be viewed together at https://raw.githubusercontent.com/be5invis/Iosevka/master/images/opentype.png . The choices specified on line 25 correspond to cv27, cv05, cv24, cv26, and cv14, respectively.

Eremiell commented on 2017-04-10 10:42 (UTC)

Maybe you could elaborate a bit on how exactly is it custom? (I've read the PKGBUILD, but still some kind of pinned note with short description and possibly a comparison image link would be great. One shouldn't need to clone the repo and try to imagine.)