Github messages for voidlinux
 help / color / mirror / Atom feed
From: georgianfire <georgianfire@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: font-iosevka: update to 3.0.1
Date: Sun, 24 May 2020 03:07:44 +0200	[thread overview]
Message-ID: <20200524010744.Q7fwRbFDhU-Any0mhAZP8L-0df5y_sIbnUULNQKddUY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22157@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

New comment by georgianfire on void-packages repository

https://github.com/void-linux/void-packages/pull/22157#issuecomment-633135458

Comment:
> Any particular reason why the Quasi-Proportional (Aile, Etoile, Sparkle) variants aren't included?

No particular reason. Originally the package only contains the default sans serif style. Then I added the slab serif variant because 1) personally I use the slab serif variant in my terminal, and 2) those are the only two variants include in homebrew (https://github.com/Homebrew/homebrew-cask-fonts/tree/master/Casks) which is a indication that they can cover the need of most people.

I have no problem adding other variants needed. But I think packing all the variants in one package will make the package unnecessarily big. Maybe we can learn from arch (https://aur.archlinux.org/packages/?K=ttf-iosevka) and put each variant in a separate package. 

      parent reply	other threads:[~2020-05-24  1:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 16:08 [PR PATCH] " georgianfire
2020-05-20 19:37 ` [PR PATCH] [Merged]: " Hoshpak
2020-05-22 11:34 ` MatthiasGrandl
2020-05-23 20:37 ` georgianfire
2020-05-23 20:38 ` georgianfire
2020-05-24  0:08 ` georgianfire
2020-05-24  1:07 ` georgianfire [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200524010744.Q7fwRbFDhU-Any0mhAZP8L-0df5y_sIbnUULNQKddUY@z \
    --to=georgianfire@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).