From: tastytea via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44950@debbugs.gnu.org
Subject: bug#44950: 28.0.50; 24-bit colors not used in terminal with emacsclient
Date: Sun, 29 Nov 2020 21:01:45 +0100 [thread overview]
Message-ID: <20201129210145.72be3199@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <83ft4sknji.fsf@gnu.org>
On 2020-11-29 20:47+0200 Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 29 Nov 2020 16:56:41 +0100
> > Jabber-ID: tastytea@tastytea.de
> > From: tastytea via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >
> > When emacs is started as daemon by an init system (without COLORTERM
> > set), emacsclient -t only has 256 colors if TERM="tmux-256color" and
> > COLORTERM="truecolor".
> > When the daemon is started with COLORTERM="truecolor" everything is
> > fine (thanks to the patch in bug #41846).
> > tmux has no -direct or -24 bit terminal definition.
> >
> > To reproduce:
> > * Start daemon: COLORTERM="" emacs --fg-daemon
> > * Start emacsclient:
> > TERM="tmux-256color" COLORTERM="truecolor" emacsclient -t
>
> Isn't this a problem with the terminfo description of tmux?
I have the same problem with xfce4-terminal, rxvt-unicode and
alacritty. I can make it work in xfce4-terminal and alacritty by
setting TERM="xterm-direct" and ncurses-6.2-p20201003 has added support
for tmux-direct, but it doesn't just work.
And since emacs uses COLORTERM, I thought emacsclient could do the same?
next prev parent reply other threads:[~2020-11-29 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 15:56 bug#44950: 28.0.50; 24-bit colors not used in terminal with emacsclient tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-29 18:47 ` Eli Zaretskii
2020-11-29 20:01 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-31 14:06 ` Tim Ruffing
2021-05-31 16:19 ` Eli Zaretskii
2021-05-31 16:45 ` Tim Ruffing
2021-05-31 17:04 ` Eli Zaretskii
2021-06-06 10:36 ` Lars Ingebrigtsen
2021-07-21 12:05 ` Lars Ingebrigtsen
2021-07-21 18:39 ` Tim Ruffing
2021-10-11 12:34 ` Stefan Kangas
2021-11-11 6:15 ` Lars Ingebrigtsen
2021-11-12 19:44 ` Tim Ruffing
2021-11-13 15:10 ` Eli Zaretskii
2021-11-16 16:42 ` Tim Ruffing
2021-11-16 17:22 ` 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=20201129210145.72be3199@ventiloplattform.tastytea.de \
--to=bug-gnu-emacs@gnu.org \
--cc=44950@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tastytea@tastytea.de \
/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).