unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:31:18 +0000	[thread overview]
Message-ID: <87ttyj44cp.fsf@sebyte.me> (raw)
In-Reply-To: <83zg8bcosc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Mar 2023 18:42:43 +0200")



Quoth Eli Zaretskii <eliz@gnu.org>
on Fri, 17 Mar 2023 18:42:43 +0200:
>> From: Sebastian Tennant <sdt@sebyte.me>
>> Cc: 62237@debbugs.gnu.org
>> Date: Fri, 17 Mar 2023 16:20:19 +0000
>>
>> […]
>> The photos happen to show an Emacs I built from master a couple of
>> days ago, i.e. Emacs 30.0.50.  If you'd still like me to test branch
>> emacs-29, then let me know and I will happily do so.
>
> 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".

>> […]
>> This lead me to investigate whether or not COLORTERM was set in my
>> environment.  I'm running Debian bullseye and terminfo is installed
>> but, nevertheless, GNOME Terminal sets COLORTERM=truecolor by default.
>
> What is TERM set to on that system?

In a plain GNOME Terminal, i.e. outside screen:

 xterm-256color

>> […]
>>
>>  https://download.sebyte.me/misc/truecolor-active.png
>>  https://download.sebyte.me/misc/truecolor-inactive.png
>
> This seems to say that your terminal isn't compatible with what
> Emacs assumes under COLORTERM=truecolor.

It would seem so.

> It also says that your terminal actually supports only 88 colors.

How do you infer that?

> So you should unset COLORTERM in your environment

That's precisely the fix I discovered yesterday.

> or use another terminal emulator (like 256-color Xterm or some
> really true-color emulator).

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.

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.

Seb





  reply	other threads:[~2023-03-17 18:31 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 [this message]
2023-03-17 19:02         ` Eli Zaretskii
2023-03-17 19:50           ` Eli Zaretskii
2023-03-17 20:18             ` Sebastian Tennant

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=87ttyj44cp.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 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).