From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: font-cm-unicode-otf-0.7.0
Date: Wed, 08 Jul 2020 22:19:11 +0200 [thread overview]
Message-ID: <20200708201911.xsZ-iz2clQpSCba5Ok7dIJbPaf6Rva7Z28FfUZWFf6g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21890@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
New comment by emacsomancer on void-packages repository
https://github.com/void-linux/void-packages/pull/21890#issuecomment-655734860
Comment:
> There are enough fonts in repo. We do not aim to provide everyone's favourite. Fonts that got into because were first to or have distinctive features like targetting usually omitted scripts or whatever else reason are updated, sure.
To me it would seem more consistent either to accept reasonable fonts more generally, or to say "we're only going to have a very small set of base fonts to get the system up and running" (like x11 fonts, liberation fonts, and dejavu). But not only are there packages like Iosevka (which is indeed a great font which I use) but also the huge `google-fonts-ttf` package (which, again, I think is useful). So it ends up seeming very arbitrary to me.
Yes, of course, fonts can be installed locally, and I do. But fonts, like applications, do get updated, and it ends up just being duplicated effort for everyone to have to try to track updates if there's someone willing to maintain a package.
prev parent reply other threads:[~2020-07-08 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 20:35 [PR PATCH] " emacsomancer
2020-05-12 20:59 ` [PR PATCH] [Updated] " emacsomancer
2020-05-20 21:14 ` emacsomancer
2020-07-07 21:44 ` emacsomancer
2020-07-08 20:07 ` Chocimier
2020-07-08 20:19 ` emacsomancer [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=20200708201911.xsZ-iz2clQpSCba5Ok7dIJbPaf6Rva7Z28FfUZWFf6g@z \
--to=emacsomancer@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).