From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44118@debbugs.gnu.org
Subject: bug#44118: 28.0.50; Unwanted switch of foreground colour in *shell* buffer
Date: Mon, 22 Feb 2021 22:16:30 +0100 [thread overview]
Message-ID: <5E0E067F-67AF-4F93-A29F-8524552E802E@Web.DE> (raw)
In-Reply-To: <87lfbgf5ex.fsf@gnus.org>
> Am 22.2.2021 um 17:12 schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Could you check whether this fixes the problem you're seeing, by any chance?
It looks good. Foreground colours changed a few times upgrading old packages. Since port fell back into its old decease of building Python 3.9 I stopped its build with C-c C-c. Colours were OK after this.
I am going to build GNU Emacs again, this time with the MacPorts "native build" variant with GCC 10 (which needs to be built first). Let's see whether this makes a difference from the Apple clang version 12.0.0 built GNU Emacs…
--
Greetings
Pete
A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live.
– Bradford Angier
next prev parent reply other threads:[~2021-02-22 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 18:10 bug#44118: 28.0.50; Unwanted switch of foreground colour in *shell* buffer Peter Dyballa
2020-12-09 13:24 ` Lars Ingebrigtsen
2020-12-09 13:44 ` Peter Dyballa
2020-12-10 14:09 ` Peter Dyballa
2020-12-11 14:47 ` Lars Ingebrigtsen
2020-12-11 15:23 ` Peter Dyballa
2020-12-11 15:27 ` Lars Ingebrigtsen
2020-12-11 16:30 ` Peter Dyballa
2020-12-12 10:54 ` Lars Ingebrigtsen
2020-12-12 11:12 ` Peter Dyballa
2020-12-18 23:18 ` Lars Ingebrigtsen
2020-12-19 9:53 ` Peter Dyballa
2020-12-19 15:48 ` Lars Ingebrigtsen
2021-02-22 16:12 ` Lars Ingebrigtsen
2021-02-22 20:03 ` Peter Dyballa
2021-02-22 21:16 ` Peter Dyballa [this message]
2021-02-22 21:41 ` Lars Ingebrigtsen
2022-03-21 22:15 ` Lars Ingebrigtsen
2020-12-10 14:58 ` Peter Dyballa
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=5E0E067F-67AF-4F93-A29F-8524552E802E@Web.DE \
--to=peter_dyballa@web.de \
--cc=44118@debbugs.gnu.org \
--cc=larsi@gnus.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).