public inbox for
help / color / mirror / Atom feed
From: Ken Brown <>
Subject: Re: cygwin emacs failing siletnly
Date: Wed, 26 Nov 2014 03:21:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/25/2014 8:54 PM, Gulliver Smith wrote:
> Thanks for all of the advice on fc-cache, but it doesn't help my emacs
> run. Does anyone else have any ideas why the fonts are causing emacs
> to blow up?

You said in one of your messages of October 13 that fc-cache is failing. 
emacs-X11 is not going to be able to find any fonts if there's something wrong 
with your fontconfig setup.  You might try running fc-cache under strace to see 
if that gives any clues.


Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-11-26  3:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  0:19 Gulliver Smith
2014-10-14  0:22 ` Jim Reisert AD1C
2014-11-09 17:10 ` Gulliver Smith
2014-11-09 17:47   ` Jim Reisert AD1C
2014-11-26  1:55 ` Gulliver Smith
2014-11-26  3:21   ` Ken Brown [this message]
2014-10-14  1:16 Gulliver Smith
2014-10-14 16:03 ` Jim Reisert AD1C

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:

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

  git send-email \ \ \ \

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