From: Sebastian Tennant <sdt@sebyte.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62237@debbugs.gnu.org
Subject: bug#62237: 28.1 or higher: 24-bit true color breaks colours in Emacsen built without X under GNU Screen
Date: Fri, 17 Mar 2023 20:18:47 +0000 [thread overview]
Message-ID: <87pm973zdk.fsf@sebyte.me> (raw)
In-Reply-To: <83ilezcg3r.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Mar 2023 21:50:16 +0200")
Quoth Eli Zaretskii <eliz@gnu.org>
on Fri, 17 Mar 2023 21:02:44 +0200:
>>> No, Emacs 30 is good enough. (Your report says Emacs 28.1, which
>>> is why I asked.)
>>
>> It's easy to miss the "or higher".
>
> The "or higher" is not useful because it says nothing about the
> versions you actually tested. It could be Emacs 28.2, for example.
> Please always tell all the details without assuming that our crystal
> balls are clear enough to see them.
Fair enough. Apologies for the lack of clarity.
>>> What is TERM set to on that system?
>>
>> In a plain GNOME Terminal, i.e. outside screen:
>>
>> xterm-256color
>
> That's 256 colors, not 64-bit true-color terminal, AFAIU.
You may be right. My understanding is very limited in this area.
>>> It also says that your terminal actually supports only 88 colors.
>>
>> How do you infer that?
>
> By looking at the color names.
Ah... OK.
>>> So you should unset COLORTERM in your environment
>>
>> That's precisely the fix I discovered yesterday.
>
> Then I guess this bug can be closed?
I suppose so.
It felt like an Emacs bug because I was happily using Emacs 27.2 and
when I upgraded to 28.1, the colours were broken all of a sudden, but
yes, the fault may be with screen.
>> According to:
>>
>> https://github.com/termstandard/colors
>>
>> command:
>>
>> $ printf "\x1b[38;2;255;100;0mTRUECOLOR\x1b[0m\n"
>>
>> shows your terminal is capable of truecolor if the word TRUECOLOR is
>> printed in brown. According to the result of this test, GNOME
>> Terminal (3.38.3) _is_ truecolor enabled.
>
> Which standard of true color does it support?
I don't know how to answer this question.
>> I can observe the same broken colours in xterm (under the same
>> conditions) shipped by Debian bullseye.
>>
>> I'm sure it has to do with screen and will investigate whther or
>> not my version of screen supports truecolor.
>
> Thanks.
Haven't had time to investigate yet, but will do tomorrow.
Quoth Eli Zaretskii <eliz@gnu.org>
on Fri, 17 Mar 2023 21:50:16 +0200:
>>> What is TERM set to on that system?
>>
>> In a plain GNOME Terminal, i.e. outside screen:
>>
>> xterm-256color
>
> And what is it set to _inside_ screen?
I set it to screen.gnome in my .screenrc, but this has no bearing on
the issue, i.e. if I comment out the ‘term screen.gnome’ line in my
.screenrc, TERM is set to screen.xterm-256color (as Robert pointed
out) and the colors are still broken.
Incidentally, I use screen.gnome because it limits the colors to eight
(and I prefer the simplicity of just eight colors).
prev parent reply other threads:[~2023-03-17 20:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 9:41 bug#62237: 28.1 or higher: 24-bit true color breaks colours in Emacsen built without X under GNU Screen Sebastian Tennant
2023-03-17 12:15 ` Eli Zaretskii
2023-03-17 15:39 ` Robert Pluim
2023-03-17 16:30 ` Eli Zaretskii
2023-03-17 17:44 ` Robert Pluim
2023-03-17 18:55 ` Eli Zaretskii
2023-03-18 9:05 ` Robert Pluim
2023-03-18 9:09 ` Eli Zaretskii
2023-03-18 10:02 ` Robert Pluim
2023-03-18 10:37 ` Eli Zaretskii
2023-03-18 11:44 ` Robert Pluim
2023-03-18 13:29 ` Eli Zaretskii
2023-03-20 8:36 ` Robert Pluim
2023-03-20 8:57 ` Sebastian Tennant
2023-03-20 12:17 ` Eli Zaretskii
2023-03-20 12:15 ` Eli Zaretskii
2023-03-20 14:08 ` Robert Pluim
2023-03-20 14:23 ` Eli Zaretskii
2023-03-20 14:51 ` Robert Pluim
2023-03-20 16:26 ` Sebastian Tennant
2023-03-23 8:05 ` Eli Zaretskii
2023-03-18 10:34 ` Sebastian Tennant
2023-03-18 11:38 ` Robert Pluim
2023-03-18 15:01 ` Sebastian Tennant
2023-03-18 15:13 ` Eli Zaretskii
2023-03-18 17:56 ` Sebastian Tennant
2023-03-18 18:35 ` Sebastian Tennant
2023-03-17 16:20 ` Sebastian Tennant
2023-03-17 16:42 ` Eli Zaretskii
2023-03-17 18:31 ` Sebastian Tennant
2023-03-17 19:02 ` Eli Zaretskii
2023-03-17 19:50 ` Eli Zaretskii
2023-03-17 20:18 ` Sebastian Tennant [this message]
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=87pm973zdk.fsf@sebyte.me \
--to=sdt@sebyte.me \
--cc=62237@debbugs.gnu.org \
--cc=eliz@gnu.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 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.