unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 30435@debbugs.gnu.org, guix-devel@gnu.org,
	Pierre Neidhardt <mail@ambrevar.xyz>, hmk <hmk42@posteo.de>
Subject: bug#30435: libreoffice: Fonts don't show up after install
Date: Thu, 02 Apr 2020 17:47:03 +0200	[thread overview]
Message-ID: <871rp5opoo.fsf__13761.1062776827$1585842491$gmane$org@gnu.org> (raw)
In-Reply-To: <878sje453l.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me> ("Nicolò Balzarotti"'s message of "Thu, 02 Apr 2020 11:19:42 +0200")

Hi Nicolò,

Nicolò Balzarotti <anothersms@gmail.com> skribis:

> Hi, I wanted to add that the opposite is also true: removing a font
> without running fc-cache always makes my emacs die on start, so I agree
> that running the command automatically makes sense.

Actually, if you can capture a stack trace of Emacs, that may tell us
what part of Fontconfig to look at if we want to change it to gracefully
handle stale cache entries.

Ludo’.

  parent reply	other threads:[~2020-04-02 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 11:06 bug#30435: libreoffice: Fonts don't show up after install hmk
2020-04-02  9:09 ` Pierre Neidhardt
     [not found] ` <87a73ui78x.fsf@ambrevar.xyz>
2020-04-02  9:19   ` Nicolò Balzarotti
2020-04-02 15:46   ` Ludovic Courtès
     [not found]   ` <878sje453l.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
2020-04-02  9:37     ` John Soo
2020-04-02 15:47     ` Ludovic Courtès [this message]
     [not found]   ` <875zehopqf.fsf@gnu.org>
2020-04-02 15:59     ` Pierre Neidhardt
     [not found]     ` <87pma4l3ug.fsf@gmail.com>
     [not found]       ` <CAFHYt56MJn=rXZTqvnjNb4dQGBXx55GoZM6i+zd+SswiSUP+pQ@mail.gmail.com>
     [not found]         ` <874jrgkxhx.fsf@gmail.com>
2023-08-29  3:28           ` Maxim Cournoyer

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='871rp5opoo.fsf__13761.1062776827$1585842491$gmane$org@gnu.org' \
    --to=ludo@gnu.org \
    --cc=30435@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=hmk42@posteo.de \
    --cc=mail@ambrevar.xyz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).