unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org, sirgazil <sirgazil@zoho.com>
Subject: Re: GNOME Terminal: Horrible font after guix system reconfigure
Date: Thu, 09 Jan 2020 02:16:59 +0100	[thread overview]
Message-ID: <87woa1cttg.fsf@nckx> (raw)
In-Reply-To: <16f87b97c70.b1a5e48e48152.4966096921865190473@zoho.com>

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

Sirgazil,

sirgazil 写道:
> Maybe there is a bug with the defaults (at least with the 
> spacing)?

Yes, although the spacing is simply a side-effect of a bad or 
missing default font.  This is what variable-width (proportional) 
fonts look like when rendered as fixed-width (monospace) cells.

If you're lucky, GNOME is innocent, and a stale fontconfig cache 
is to blame.

1. Does /var/cache/fontconfig exist?  If so, remove it (you'll 
probably need sudo)
2. Regardless of step 1: run ‘fc-cache -r’ (without sudo) and
3. Open a new terminal[0]
4. …profit?

Kind regards,

T G-R

[0]: I don't know whether GNOME terminal tries to be clever by 
opening new windows in the same process, so do make sure you're 
actually starting a fresh instance.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-01-09  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  0:34 GNOME Terminal: Horrible font after guix system reconfigure sirgazil
2020-01-09  1:16 ` Tobias Geerinckx-Rice [this message]
2020-01-09 14:21   ` sirgazil
2020-01-09  8:47 ` Christopher Baines
2020-01-09 14:23   ` sirgazil
2020-02-12 13:58 ` Ludovic Courtès
2020-02-12 23:55   ` Christopher Baines
2020-02-13  4:26     ` Gábor Boskovits
2020-02-13 18:09       ` sirgazil
2020-02-13 21:46         ` Gábor Boskovits

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87woa1cttg.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=sirgazil@zoho.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).