From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 62237-done@debbugs.gnu.org, sdt@sebyte.me
Subject: bug#62237: 28.1 or higher: 24-bit true color breaks colours in Emacsen built without X under GNU Screen
Date: Thu, 23 Mar 2023 10:05:27 +0200 [thread overview]
Message-ID: <83a6036gfs.fsf@gnu.org> (raw)
In-Reply-To: <87y1nrpjbk.fsf@gmail.com> (message from Robert Pluim on Mon, 20 Mar 2023 15:51:27 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: sdt@sebyte.me, 62237@debbugs.gnu.org
> Date: Mon, 20 Mar 2023 15:51:27 +0100
>
> >>>>> On Mon, 20 Mar 2023 16:23:28 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> COLORTERM support was added because it reportedly helped in some
> Eli> real-life cases. If it turns out it gets in the way in other cases,
> Eli> we need either find a way of detecting those problematic cases where
> Eli> we process COLORTERM, or ask users to unset the variable if it causes
> Eli> trouble. I don't see how we could defer processing COLORTERM to
> Eli> later, as knowing how many colors Emacs can work with is necessary
> Eli> very early into startup; too many things will break or work
> Eli> incorrectly if we defer that to later.
>
> OK. Still sounds like etc/PROBLEMS to me :-)
I have now added a PROBLEMS entry about this issue on the emacs-29
branch, and I'm closing this bug.
Thank you both for all the useful information about the various
aspects of the issue. I tried to use all of that in the PROBLEMS
entry.
next prev parent reply other threads:[~2023-03-23 8:05 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 [this message]
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
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=83a6036gfs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62237-done@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=sdt@sebyte.me \
/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).