From: Eli Zaretskii <eliz@gnu.org>
To: George Nachman <gnachman@llamas.org>
Cc: dancol@dancol.org, emacs-devel@gnu.org
Subject: Re: What capabilities do you wish terminal emulators would report?
Date: Fri, 15 May 2020 14:19:26 +0300 [thread overview]
Message-ID: <834ksh30ox.fsf@gnu.org> (raw)
In-Reply-To: <CAB5Rqom3os8+V3PPJ8hWB-r-QubfYxEw7nffPb4QWCDAWKFP9A@mail.gmail.com> (message from George Nachman on Sat, 9 May 2020 12:41:45 -0700)
> From: George Nachman <gnachman@llamas.org>
> Date: Sat, 9 May 2020 12:41:45 -0700
> Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
>
> Please respond on this thread and I'll update the spreadsheet, or else add a comment to the spreadsheet. I
> don't want to open up write access to the world because that would be total chaos.
Color capabilities: Emacs supports 24-bit colors on capable terminals.
OSC 52: I think Emacs supports that on capable terminals, but I'm
confused by the references to base-64 encoding there, so maybe I'm
wrong.
SGR mouse: Emacs has full support for the mouse.
UTF-8 support: Check.
AMBIGUOUS_FULLWIDTH: Not quite sure what this is about, but Emacs does
support fullwidth characters per East-Asian Width defined by the
latest Unicode Standard.
Unicode version: Emacs supports the latest one.
RTL/BIDI: Emacs supports bidirectional editing per UAX#9 of the latest
Unicode Standard version.
Title setting: Supported.
Bracketed paste: Supported.
Focus reporting: Supported.
prev parent reply other threads:[~2020-05-15 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 7:34 What capabilities do you wish terminal emulators would report? George Nachman
2020-05-08 10:20 ` Eli Zaretskii
2020-05-08 14:30 ` Eli Zaretskii
2020-05-08 15:25 ` Stefan Monnier
2020-05-08 18:29 ` Daniel Colascione
2020-05-08 20:51 ` George Nachman
2020-05-09 6:09 ` Eli Zaretskii
2020-05-09 19:41 ` George Nachman
2020-05-15 11:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834ksh30ox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=gnachman@llamas.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.