From: Lars Ingebrigtsen <larsi@gnus.org>
To: salvomicciche` <salvo@biancavela.it>
Cc: 45940@debbugs.gnu.org
Subject: bug#45940: Emacs in macOS: Failed to initialise color...
Date: Tue, 19 Jan 2021 08:17:22 +0100 [thread overview]
Message-ID: <87r1mhl7jx.fsf@gnus.org> (raw)
In-Reply-To: <C23804F8-A99C-48E7-AE39-BB7281E6E594@biancavela.it> (salvomicciche`'s message of "Tue, 19 Jan 2021 08:06:16 +0100")
(Please keep the debbugs address in the CCs -- otherwise the bug tracker
won't receive the message. Resent for the bug tracker.)
salvomicciche` <salvo@biancavela.it> writes:
> Andrii, sorry, but the hint
>
> «rm $HOME/Library/Colors/Emacs.clr
> Then restart Emacs twice. The first time it will recreate the file and
> probably not emit any error, the second time should let us know if the
> error has gone»
> doesn’t solve my problem. After deleting that file and restarted Emacs, here the program re-create that file (Emacs.clr) again and the message won’t go off.
>
> Thanks for help, best regards,
> Salvo
>
> Il giorno 19 gen 2021, alle ore 05:51, Lars Ingebrigtsen <larsi@gnus.org> ha
> scritto:
>
> Andrii Kolomoiets <andreyk.mad@gmail.com> writes:
>
> See Bug#32854
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32854
>
> So the suggestion there was:
>
> What I’d suggest to Evan is to delete the colour file, as it’s
> possible Emacs 26.1 has left a corrupt version:
>
> rm $HOME/Library/Colors/Emacs.clr
>
> Then restart Emacs twice. The first time it will recreate the file and
> probably not emit any error, the second time should let us know if the
> error has gone.
>
> Salvo, does this solve the problem for you, too?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-19 7:17 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 [this message]
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
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
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=87r1mhl7jx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45940@debbugs.gnu.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 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).