From: Eli Zaretskii <eliz@gnu.org>
To: "Rami Ylimäki" <rami.ylimaki@vincit.fi>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH 0/1] Proper 24-bit TTY detection for Emacs 26.
Date: Mon, 29 Jan 2018 17:59:26 +0200 [thread overview]
Message-ID: <83h8r4irkx.fsf@gnu.org> (raw)
In-Reply-To: <4ba09000-896f-9950-f99c-f46f431f490f@vincit.fi> (message from Rami Ylimäki on Mon, 29 Jan 2018 15:27:37 +0200)
> Cc: emacs-devel@gnu.org
> From: Rami Ylimäki <rami.ylimaki@vincit.fi>
> Date: Mon, 29 Jan 2018 15:27:37 +0200
>
> The "set[bf]24" capabilities are only supported by Emacs, because
> traditionally Terminfo hasn't offered any way to detect direct color
> support. This workaround forces users to compile their own TERMs with
> these capabilities.
>
> Latest Terminfo provides several TERMs with "-direct" suffix, such as
> "xterm-direct", that support "RGB" with "seta[bf]". We definitely want
> to support this.
OK, thanks for explaining the situation.
> I can open a bug about this and post a patch that supports both methods
> on Emacs 27, since it's too late for 26.
Please do, and thanks.
> There might be some problems with Emacs 26 and TERM=xterm-direct, but I
> haven't properly investigated this yet. At least I already noticed some
> error messages from xterm.el:xterm-register-default-colors.
If there's a reasonable workaround for those problems, we could
perhaps describe it in etc/PROBLEMS for Emacs 26.
prev parent reply other threads:[~2018-01-29 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 20:05 [PATCH 0/1] Proper 24-bit TTY detection for Emacs 26 Rami Ylimäki
2018-01-23 20:05 ` [PATCH 1/1] Detect 24-bit TTY color support with standard Terminfo capabilites Rami Ylimäki
2018-01-24 18:39 ` [PATCH 0/1] Proper 24-bit TTY detection for Emacs 26 Eli Zaretskii
2018-01-29 13:27 ` Rami Ylimäki
2018-01-29 15:59 ` Eli Zaretskii [this message]
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=83h8r4irkx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rami.ylimaki@vincit.fi \
/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).