Github messages for voidlinux
 help / color / mirror / Atom feed
From: c0m4r <c0m4r@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gsettings-desktop-schemas: missing font dependency
Date: Wed, 31 Jan 2024 18:11:19 +0100	[thread overview]
Message-ID: <20240131171119.41416246B4@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48382@inbox.vuxu.org>

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

New comment by c0m4r on void-packages repository

https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919545113

Comment:
> The schema also references Cantarell, but GTK applications with client-side decorations still seem to function with an alternative font.

That's correct, however that's not the case in terminal emulators. You either need to provide the correct font or change the configuration pointing to the generic Monospace font (Debian does that). The idea is so it just works by default, without such changes.

> It would seem better to have the default schema reference generic font aliases rather than specific fonts.

It depends. I compared solutions used by other distros and I found this font as a dep less invasive and problematic. It's widely used and you don't need to modify schemas, nor configuration. By changing the default schemas there's no guarantee that it's not already overwritten by the local or user configuration, still pointing to the missing font. Moreover, this way we use native, consistent fonts. So in terms of user experience I'd vote for adding missing font the way that [Arch](https://archlinux.org/packages/extra/any/gsettings-desktop-schemas/) does that, rather that the overwriting schemas.

  parent reply	other threads:[~2024-01-31 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 16:27 [PR PATCH] " c0m4r
2024-01-31 16:09 ` ahesford
2024-01-31 17:11 ` c0m4r [this message]
2024-01-31 17:14 ` c0m4r
2024-01-31 18:20 ` ahesford
2024-01-31 19:39 ` c0m4r
2024-02-02  7:38 ` [PR PATCH] [Closed]: " c0m4r

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=20240131171119.41416246B4@inbox.vuxu.org \
    --to=c0m4r@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).