From: Alan Third <alan@idiocy.org>
To: salvomicciche` <salvo@biancavela.it>
Cc: 45940@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#45940: Emacs in macOS: Failed to initialise color...
Date: Tue, 19 Jan 2021 23:06:06 +0000 [thread overview]
Message-ID: <YAdl3uRLua7TgLPX@breton.holly.idiocy.org> (raw)
In-Reply-To: <9759C782-4ED6-4F7D-AFBD-BA2B54630A9E@biancavela.it>
On Tue, Jan 19, 2021 at 09:52:43PM +0100, salvomicciche` wrote:
> thank you, Alan,
> your solution worked!
> It was a file, really: PANTONE+ Solid Uncoated-V2.clr (attached here, data: 2016).
> If I remove this Emacs generate its file and no error or warning happens.
> If think I could remove the files, as I’ve also another file, PANTONE+ Solid Uncoated-V3.clr (2019) that should be the replacement…
>
> Now Emacs doesn’t generate the warning.
Excellent, thanks for letting us know.
I think Apple changed the format of the files a while back, which is
what caused us our first problems with this.
Emacs 28 will already rebuild the Emacs.clr file if it's incorrect,
but other files are out of our control, so I suppose the right thing
for Emacs to do here is to silently ignore errors.
--
Alan Third
next prev parent reply other threads:[~2021-01-19 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 16:07 bug#45940: Emacs in macOS: Failed to initialise color salvomicciche`
2021-01-17 20:25 ` Andrii Kolomoiets
2021-01-19 4:51 ` Lars Ingebrigtsen
[not found] ` <C23804F8-A99C-48E7-AE39-BB7281E6E594@biancavela.it>
2021-01-19 7:17 ` Lars Ingebrigtsen
2021-01-19 7:22 ` salvomicciche`
2021-01-19 7:28 ` Lars Ingebrigtsen
2021-01-19 7:32 ` salvomicciche`
2021-01-19 7:36 ` Lars Ingebrigtsen
2021-01-19 7:37 ` salvomicciche`
2021-01-19 11:22 ` salvomicciche`
2021-01-19 20:41 ` Alan Third
2021-01-19 20:52 ` salvomicciche`
2021-01-19 23:06 ` Alan Third [this message]
2021-01-20 1:47 ` Lars Ingebrigtsen
2021-01-23 10:44 ` Alan Third
2021-01-23 19:09 ` Lars Ingebrigtsen
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=YAdl3uRLua7TgLPX@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=45940@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=salvo@biancavela.it \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.