From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Cl=C3=A9ment?= Pit-Claudel Newsgroups: gmane.emacs.bugs Subject: bug#34606: Emacs colors are off in screen sessions Date: Thu, 21 Feb 2019 11:37:25 -0500 Message-ID: References: <863a6869-ee18-f49d-68e3-2a1d86c648ed@gmail.com> <83pnrlf9ro.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="93260"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 Cc: 34606@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Feb 21 17:38:20 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwrMY-000O7p-Cr for geb-bug-gnu-emacs@m.gmane.org; Thu, 21 Feb 2019 17:38:18 +0100 Original-Received: from localhost ([127.0.0.1]:34700 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwrMX-00037V-3Y for geb-bug-gnu-emacs@m.gmane.org; Thu, 21 Feb 2019 11:38:17 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:50653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwrMJ-00036a-Fr for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2019 11:38:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwrMI-0007pz-QJ for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2019 11:38:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59011) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gwrMI-0007ph-Ly for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2019 11:38:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gwrMI-0005Sr-Cg for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2019 11:38:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 21 Feb 2019 16:38:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34606 X-GNU-PR-Package: emacs Original-Received: via spool by 34606-submit@debbugs.gnu.org id=B34606.155076705620973 (code B ref 34606); Thu, 21 Feb 2019 16:38:02 +0000 Original-Received: (at 34606) by debbugs.gnu.org; 21 Feb 2019 16:37:36 +0000 Original-Received: from localhost ([127.0.0.1]:59777 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gwrLs-0005SD-2X for submit@debbugs.gnu.org; Thu, 21 Feb 2019 11:37:36 -0500 Original-Received: from mail-qt1-f172.google.com ([209.85.160.172]:34794) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gwrLp-0005S0-Vx for 34606@debbugs.gnu.org; Thu, 21 Feb 2019 11:37:34 -0500 Original-Received: by mail-qt1-f172.google.com with SMTP id w4so32254414qtc.1 for <34606@debbugs.gnu.org>; Thu, 21 Feb 2019 08:37:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HV5itK7CkifTzDsD6uevytffVbO+1HjcZunZc4v+pnc=; b=mk9FZ9KdM9j3bsaRZu/KryOpDWWABwrSiu+M98ohsTxPJKJMQNidRblQVzyX2e39k4 sVp7TUDcxZdP81sna4SMTHSj05WIfOhIxMnam/kF71iFF/dp61ADj4iSvrrsvYN+AtTL IaPvy5lPlwkyqYJ9v9An2UXpEsmRgPxPxBqPx8GiL83/UdLXcc1qRITR6nhSd1qQ6N4G dZgZgr5gC+WxJB76cfooVeZ3S1oacFpqkmmH6QnTYwd7t4hhmsSIW7/QRXUQDJbJ0CPn jvrmEW9Hji+C4v5RzpgQ9rzqzk3yy4Xz9WGnGmOL1cVdgl6XlHNfbLvU9tk0FiHJxe// f51Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HV5itK7CkifTzDsD6uevytffVbO+1HjcZunZc4v+pnc=; b=jcPhCU2wf9CvxMqhXKVaQc7PJDWJiMKPh0w9qYZjDz+OIhrQ9wAvwWg5UGN1zK8FZi LogQ0itVlcxApbJpGrgPZLCMVnwQFBuYVMepLrdSQDiOa34EFUZsjJqIVNnNCGaRTTce uSu1dIMQetxDC/l7cShgig2wWGcweGxpWsEVvgHcqa5YLMcMKXeieUGEYl/EJgxOSlE0 a6RVUWQLNJMxeKGs++CyC/ZBsc/VYGCYaS/gLRHn557jSj2lWcQQRj8oZS50r2iwuWgF IvFWo78EUGKIpDqP4sp+7kdgxBnFiCMLhMeFN5tdyey1/UOTBQj/Qul+aX6OsX/+fnx1 3fzg== X-Gm-Message-State: AHQUAubcO5JU42pMyEDGSh1JejwCEyLDg1KenEg3lVciTyyaarsm0NGO Co6dw5x9KahXT63Kzy1WqXtm+25V X-Google-Smtp-Source: AHgI3IakZgOy1nNlWPFDFIeapZ/60nzJjHNtCdedVggZbeYiMItiJ3Sg8xwneSqRmqbFRVY/IlOn+g== X-Received: by 2002:ac8:2427:: with SMTP id c36mr32835002qtc.124.1550767047331; Thu, 21 Feb 2019 08:37:27 -0800 (PST) Original-Received: from ?IPv6:2601:184:4180:66e7:7153:e8ef:c4f6:5d09? ([2601:184:4180:66e7:7153:e8ef:c4f6:5d09]) by smtp.googlemail.com with ESMTPSA id v131sm12854270qka.95.2019.02.21.08.37.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Feb 2019 08:37:26 -0800 (PST) In-Reply-To: <83pnrlf9ro.fsf@gnu.org> Content-Language: en-GB X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:155622 Archived-At: On 21/02/2019 10.20, Eli Zaretskii wrote: >> From: Clément Pit-Claudel >> Date: Thu, 21 Feb 2019 09:56:18 -0500 >> >> Is this all as expected? Why does changing to xterm-256color yield different results with or without ncurses-term? If I understand correctly, the reason why TERM changes after I install ncurses-term is that this package provides the screen.xterm-256color termcap entry, and then screen acts as documented: >> >> When screen tries to figure out a terminal name for itself, it first looks for an entry named "screen.", >> where is the contents of your $TERM variable. If no such entry exists, screen tries "screen" (…) >> >> Is there anything that Emacs could do differently to make things smoother? In particular, could TERM=screen.xterm-256color behave the same as TERM=screen-256color? > > Emacs on a TTY doesn't control the colors in RGB terms, it just tells > the terminal to display color number N. What you actually see as > result is up to the terminfo entry and the terminal emulator, AFAIK > mostly the latter. So I'd suggest to dig into 'screen's > customizations to see how to affect the colors (I customized the > colors of PuTTY to get something I like, for example). I don't understand. If that is the case, how can changing the value of the TERM environment variable change the colors displayed by emacs?