unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Ruffing <crypto@timruffing.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tastytea@tastytea.de, larsi@gnus.org, 44950@debbugs.gnu.org
Subject: bug#44950: 28.0.50; 24-bit colors not used in terminal with emacsclient
Date: Tue, 16 Nov 2021 17:42:32 +0100	[thread overview]
Message-ID: <9f08184d088ac08c3ce4c589e521bcc9590474ec.camel@timruffing.de> (raw)
In-Reply-To: <83a6i8xf9a.fsf@gnu.org>

On Sat, 2021-11-13 at 17:10 +0200, Eli Zaretskii wrote:
> > I personally don't care too much. With the Tc fix applied, Emacs
> > works
> > for me, and believe our current code is fine, even though we don't
> > fully replicate tmux's logic respect to Tc. On the other hand, with
> > full support for setrgbf/setrgbb, we'd support pretty much every
> > existing method out there and the diff is not that large.
> 
> I'm not sure I understand: if supporting "Tc" does the job, what does
> the added code gain us?

Well, there are just (too) many standards and without setrgbf/setrgbb,
we don't support all of them. Even with support for Tc, there may be
terminals which can do 24bit but don't have Tc in their terminfo but
only setrgbf/setrgbb.

It's also possible (but very unlikely?) that they support only non-
"standard" escape sequences and thus can have setrgbf/setrgbb with non-
default sequences in terminfo but not Tc because the latter implies the
"standard" escape sequence. 

As I said, I believe the current code does the job. But still, I
wouldn't be surprised if next year some user proves me wrong and
complains here that 24bit doesn't work with their specific rare
terminal/terminfo while it works in other programs (which support
setrgbf/setrgbb).






  reply	other threads:[~2021-11-16 16:42 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
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 [this message]
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=9f08184d088ac08c3ce4c589e521bcc9590474ec.camel@timruffing.de \
    --to=crypto@timruffing.de \
    --cc=44950@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).