From: Sebastian Tennant <sdt@sebyte.me>
To: 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 09:41:36 +0000 [thread overview]
Message-ID: <87sfe390kv.fsf@sebyte.me> (raw)
Hello there,
Summary: Support for 24-bit true colour, added in Emacs 28.1, breaks
colours in Emacsen built without X support and running under
GNU Screen (v4.08.00).
Steps to reproduce:
1. Build Emacs >= 28.1 without X support. The two configurations I have
tested are below:
./configure\ ./configure\
--prefix=[…]\ --prefix=[…]\
--enable-check-lisp-object-type\ --enable-check-lisp-object-type\
--disable-acl\ --disable-acl\
--without-dbus\ --without-all\
--without-gconf\ --without-x\
--without-gif\ --with-file-notification=yes\
--without-gsettings\ --with-gnutls\
--without-jpeg\ --with-gpm\
--without-modules\ --with-json\
--without-png\ --with-mailutils\
--without-rsvg\ --with-modules\
--without-selinux\ --with-native-compilation\
--without-sound\ --with-libsystemd\
--without-tiff\ --with-small-ja-dic\
--without-x\ --with-sqlite3\
--without-xpm\ --with-threads\
--with-xml2\
--with-zlib\
2. Launch a terminal program (e.g. GNOME Terminal) and run GNU Screen
(bypassing any .screenrc):
$ touch foo
$ screen -c foo
3. Run Emacs with 24-bit true colour active and observe the broken colours:
$ COLORTERM=truecolor ./src/emacs -Q
Screenshot: https://download.sebyte.me/misc/truecolor-active.png
4. Run Emacs with 24-bit true colour inactive and observe the correct colours:
$ COLORTERM= ./src/emacs -Q
Screenshot: https://download.sebyte.me/misc/truecolor-inactive.png
next reply other threads:[~2023-03-17 9:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 9:41 Sebastian Tennant [this message]
2023-03-17 12:15 ` bug#62237: 28.1 or higher: 24-bit true color breaks colours in Emacsen built without X under GNU Screen 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
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=87sfe390kv.fsf@sebyte.me \
--to=sdt@sebyte.me \
--cc=62237@debbugs.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).