From: Alan Third <alan@idiocy.org>
To: Bob Halley <halley@play-bow.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: High Sierra Beta 5 Display Problems
Date: Tue, 8 Aug 2017 23:13:27 +0100 [thread overview]
Message-ID: <20170808221327.GA83361@breton.holly.idiocy.org> (raw)
In-Reply-To: <7ED9D2F9-FDC0-40C9-B992-120202E46D6F@play-bow.org>
On Tue, Aug 08, 2017 at 01:50:38PM -0700, Bob Halley wrote:
> The color table it is loading appears to be stored in
> ~/Library/Colors/Emacs.clr. There is no difference between the file
> that I had there before any of this happened and the file it writes
> when I force it to run the "rebuild it from the rgb.txt" path. (I
> checked this by restoring from a backup.) If I start an unhacked
> Emacs and ~/Library/Colors/Emacs.clr does not exist, then Emacs
> launches correctly with proper colors. It also recreates the file.
> Subsequent starts of Emacs always result in the broken colors.
Hi Bob, is there anything else in ~/Library/Colors? From the looks of
the code in ns_get_color Emacs searches *all* colour lists for any
that contain the name it’s looking for, not just Emacs.clr. Maybe
there’s a corrupt one that’s causing the search to fail early?
I can’t think of anything else. From the documentation it doesn’t look
like anything has changed, but perhaps Apple just aren’t listing High
Sierra changes yet...?
--
Alan Third
next prev parent reply other threads:[~2017-08-08 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 15:44 High Sierra Beta 5 Display Problems Bob Halley
2017-08-08 18:46 ` Eli Zaretskii
2017-08-08 19:20 ` Bob Halley
2017-08-08 19:39 ` Eli Zaretskii
2017-08-08 19:56 ` Bob Halley
2017-08-08 20:21 ` Bob Halley
2017-08-08 20:50 ` Bob Halley
2017-08-08 22:13 ` Alan Third [this message]
2017-08-08 22:33 ` Bob Halley
2017-08-08 22:51 ` Bob Halley
2017-08-14 21:32 ` Herbert J. Skuhra
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170808221327.GA83361@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=halley@play-bow.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).