From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.bugs 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:44:19 +0100 Message-ID: <87sfe3s26k.fsf@gmail.com> References: <87sfe390kv.fsf@sebyte.me> <83h6ujefq1.fsf@gnu.org> <87wn3fs7yw.fsf@gmail.com> <833563e3xc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18389"; mail-complaints-to="usenet@ciao.gmane.io" Cc: sdt@sebyte.me, 62237@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 17 18:45:27 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pdE8t-0004W7-CM for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 17 Mar 2023 18:45:27 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pdE8Y-0002Jm-KV; Fri, 17 Mar 2023 13:45:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pdE8V-0002JV-Oe for bug-gnu-emacs@gnu.org; Fri, 17 Mar 2023 13:45:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pdE8U-00085v-GB for bug-gnu-emacs@gnu.org; Fri, 17 Mar 2023 13:45:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pdE8T-0001UE-T2 for bug-gnu-emacs@gnu.org; Fri, 17 Mar 2023 13:45:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Robert Pluim Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 17 Mar 2023 17:45:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62237 X-GNU-PR-Package: emacs Original-Received: via spool by 62237-submit@debbugs.gnu.org id=B62237.16790750695654 (code B ref 62237); Fri, 17 Mar 2023 17:45:01 +0000 Original-Received: (at 62237) by debbugs.gnu.org; 17 Mar 2023 17:44:29 +0000 Original-Received: from localhost ([127.0.0.1]:45563 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pdE7w-0001T8-JC for submit@debbugs.gnu.org; Fri, 17 Mar 2023 13:44:28 -0400 Original-Received: from mail-wr1-f46.google.com ([209.85.221.46]:43705) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pdE7v-0001Su-2b for 62237@debbugs.gnu.org; Fri, 17 Mar 2023 13:44:27 -0400 Original-Received: by mail-wr1-f46.google.com with SMTP id l12so5154432wrm.10 for <62237@debbugs.gnu.org>; Fri, 17 Mar 2023 10:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679075061; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=221RX4HHxE2jTFSxStPS8TYkzbvxIt7u8SjOUGwQcpU=; b=HO84lBZqvgeOR8ele3tqXejBibbndAX04zk4UurOJg7LJNGbeFNqUN5nNnFmwrts0f eknuStY9G/NDHO0qoUmQ1uqbo25/pZ+IK0/E4xMeFpSrNLWeQnhdba7G5pXw90E28wPp CDsJVqfdCBi4JrBVt4gyYySeBIo9vuZ8S0OG8+xvQ7rDBSrftjEeoZq+5hwCvLUQFtyF B7McOJTcTdsAI5bRigJ2KQpzm/xGP9teq5djWyAOezYX8X3FZ67IGkvvaPw5yIWSVmKq i5haGUL6vQPZNYUqy8mmDrd6AicDGXaGpBsiWWzYtMq5jo4Es7J6tq6Vf5WT+Q66fSmH dQuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679075061; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=221RX4HHxE2jTFSxStPS8TYkzbvxIt7u8SjOUGwQcpU=; b=ZdhvW7S/IAg0HXMUfYtUoMlNWDBoGpKiXM3S7umn1h/NiPdPYar1NW/AunegEX3Ojs R1xxcDhdXsQjJyqV6zdo8qUXefeFs5y/AfX/JPIlSlZLHkxwHtlphfoJU3UoB4/pJo1i +FJLULERT4UEz11DOTfpcIfFBFE7fyOqihbVo3c1EVTzvXyxcMP6NJxZqL03Mey9J+z9 wMlkwFDk43UazOEUZ/mTc+9LFEFp3qB8S4BBmQ3jskM9BvDgTHKTF0N5zbhHIa7/AARx ox2qo7xVsElXINYtLPpQEBonhkI4k3eC7Xc9hC7Hzc++7s+Ib+ANq7ee02T6WeB5eb9+ WLHA== X-Gm-Message-State: AO0yUKUp5CelKGNejwIlNspgUb0Ge64JnFiSve0M1VwXGOfoTFHdwNFc I7wBciYlgcAsvB2xHbYQaejmT/AM6C8= X-Google-Smtp-Source: AK7set8CxO6DCpNDNNTB5KUpeF/u9NaQvFj+Wbfa5Mm/bmDQKow4ljxeiWDK19xZGY0IIgndq0K34w== X-Received: by 2002:a5d:522b:0:b0:2cf:e67c:8245 with SMTP id i11-20020a5d522b000000b002cfe67c8245mr7891618wra.44.1679075060589; Fri, 17 Mar 2023 10:44:20 -0700 (PDT) Original-Received: from rltb ([82.66.8.55]) by smtp.gmail.com with ESMTPSA id f11-20020a5d4dcb000000b002cfe3f842c8sm2442865wru.56.2023.03.17.10.44.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Mar 2023 10:44:20 -0700 (PDT) In-Reply-To: <833563e3xc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Mar 2023 18:30:23 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:258100 Archived-At: >>>>> On Fri, 17 Mar 2023 18:30:23 +0200, Eli Zaretskii said: >> From: Robert Pluim >> Cc: Sebastian Tennant , 62237@debbugs.gnu.org >> Date: Fri, 17 Mar 2023 16:39:19 +0100 >>=20 >> For reasons unknown to me, I actually have COLORTERM=3Dtruecolor set= in >> my environment, which tickles this issue. But the only reason it does >> so is because under screen by default I get >> TERM=3Dscreen.xterm-256color. If I do >>=20 >> TERM=3Dxterm-256color src/emacs -Q -nw >>=20 >> then I get 24bit colour (according to `display-color-cells') >>=20 >> I guess we could drop the 'screen.' prefix in >> `init_display_interactive', although that does feel like a hack. Eli> Why not in screen.el? Because the 24 bit colour detection is done in init_tty. By the time we get to screen.el it=CA=BCs too late. Eli> Is this screen.FOO format documented somewhere in screen's Eli> documentation? Yes: When screen tries to figure out a terminal name for itself, it fi= rst looks for an entry named "screen.", where is the conte= nts of your $TERM variable. If no such entry exists, screen tries "scre= en" (or "screen-w" if the terminal is wide (132 cols or more)). If e= ven this entry cannot be found, "vt100" is used as a substitute. The idea is that if you have a terminal which doesn't support an imp= or=E2=80=90 tant feature (e.g. delete char or clear to EOS) you can build a = new termcap/terminfo entry for screen (named "screen.") in wh= ich this capability has been disabled. If this entry is installed on y= our machines you are able to do a rlogin and still keep the correct te= rm=E2=80=90 --> cap/terminfo entry. The terminal name is put in the $TERM variable= of all new windows. Screen also sets the $TERMCAP variable reflecting = the capabilities of the virtual terminal emulated. Notice that, however,= on machines using the terminfo database this variable has no effect. F= ur=E2=80=90 thermore, the variable $WINDOW is set to the window number of each w= in=E2=80=90 dow. Robert --=20