From: Lars Ingebrigtsen <larsi@gnus.org>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: 44118@debbugs.gnu.org
Subject: bug#44118: 28.0.50; Unwanted switch of foreground colour in *shell* buffer
Date: Fri, 11 Dec 2020 15:47:16 +0100 [thread overview]
Message-ID: <87sg8c9z7v.fsf@gnus.org> (raw)
In-Reply-To: <4E1164EC-8828-4A6D-B135-C94969D90C87@Web.DE> (Peter Dyballa's message of "Thu, 10 Dec 2020 15:09:23 +0100")
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Can you reproduce this problem with an emacs started with "emacs -Q"?
>
> Yes, it just happened:
Hm... does your Emacs really look like that when you start it with
"emacs -Q"? Hm... Oh, I see -- it's an "emacs -nw" and those are the
colours in your terminal?
And the blue "root 235 /\" is your shell prompt? Are there any ANSI
codes in your prompt? I don't quite see why that would affect the
output here in this way, but it's one more thing that would be nice to
eliminate -- could you use the default OS shell prompt and see whether
that changes anything?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-11 14:47 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 [this message]
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
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=87sg8c9z7v.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44118@debbugs.gnu.org \
--cc=Peter_Dyballa@Web.DE \
/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).