From: Eli Zaretskii <eliz@gnu.org>
To: "Vojtěch Balák" <vojtech@balak.me>
Cc: 62528@debbugs.gnu.org
Subject: bug#62528: 28.2; Emacsclient doesn't use COLORTERM
Date: Wed, 29 Mar 2023 20:21:33 +0300 [thread overview]
Message-ID: <837cuz79sy.fsf@gnu.org> (raw)
In-Reply-To: <998d09cc-292e-4c14-a14c-2d1ad0e3ab34@betaapp.fastmail.com> (message from Vojtěch Balák on Wed, 29 Mar 2023 17:06:18 +0200)
> Date: Wed, 29 Mar 2023 17:06:18 +0200
> From: Vojtěch Balák <vojtech@balak.me>
>
> When starting Emacs in a terminal emulator with 24 bit color support,
> I would like it to take advantage of this. According to the FAQ
> section 5.3, setting the variable COLORTERM to truecolor should
> result in Emacs using 24 bit colors. But according to my observations,
> this is not always true.
>
> Starting Emacs in these ways does result in it using true color:
> TERM=xterm-256color COLORTERM=truecolor emacs -nw
> TERM=xterm-direct COLORTERM= emacs -nw
> TERM=xterm-direct COLORTERM= emacsclient -nw
>
> Starting it in these ways does result in it NOT using true color:
> TERM=xterm-256color COLORTERM= emacs -nw
> TERM=xterm-256color COLORTERM= emacsclient -nw
> TERM=xterm-256color COLORTERM=truecolor emacsclient -nw
>
> The last one is the odd one out. According to my understanding, that
> should result in 24 bit color being used, but in practice it does not.
I think you are misinterpreting what the documentation says.
COLORTERM=truecolor can only affect Emacs, it cannot affect the
display triggered by emacsclient.
next prev parent reply other threads:[~2023-03-29 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 15:06 bug#62528: 28.2; Emacsclient doesn't use COLORTERM Vojtěch Balák
2023-03-29 17:21 ` Eli Zaretskii [this message]
2023-03-29 18:42 ` Vojtěch Balák
2023-03-29 18:48 ` Eli Zaretskii
2023-03-30 7:49 ` Vojtěch Balák
2023-03-30 8:51 ` Eli Zaretskii
2023-03-30 8:59 ` Robert Pluim
2023-03-30 9:34 ` Eli Zaretskii
2023-03-30 9:41 ` Robert Pluim
2023-03-30 10:36 ` Eli Zaretskii
2023-03-30 12:11 ` Robert Pluim
2023-03-30 14:14 ` Eli Zaretskii
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=837cuz79sy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62528@debbugs.gnu.org \
--cc=vojtech@balak.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).