From: George Nachman <gnachman@llamas.org>
To: emacs-devel@gnu.org
Subject: What capabilities do you wish terminal emulators would report?
Date: Fri, 8 May 2020 00:34:27 -0700 [thread overview]
Message-ID: <CAB5Rqom-yxMcAgiNo=F1-MjhxqNQ2qRKzvxN1muBFdougATrNw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Some terminal emulator authors (VTE, xterm, tmux, mintty, libvterm, iTerm2,
and others) are discussing building a new mechanism for reporting
capabilities. For context: https://github.com/mintty/mintty/issues/881
My goal is to collect desires from developers of popular applications. What
capabilities do you wish you could discover about terminals that you don't
already get from terminfo?
For example, being able to detect 24-bit color support, available cursor
styles, bracketed paste support, and mouse reporting modes are the kinds of
capabilities that would be included. They would likely be exposed through a
combination of a new environment variable and a to-be-determined control
sequence that reports them.
The results of this survey are being collected here:
https://docs.google.com/spreadsheets/d/1H4OK8z98ptySnAPjlej56lrL6b0S1j6okwp7KLRTDBQ/edit#gid=0
If you prefer not to use Google Docs, I have a PDF of its current contents
here: https://iterm2.com/misc/TerminalFeaturesCandidates1.pdf
Thanks in advance for your time, and apologies if this is the wrong forum
for this query—please redirect me if so!
-George
[-- Attachment #2: Type: text/html, Size: 1451 bytes --]
next reply other threads:[~2020-05-08 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 7:34 George Nachman [this message]
2020-05-08 10:20 ` What capabilities do you wish terminal emulators would report? 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
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='CAB5Rqom-yxMcAgiNo=F1-MjhxqNQ2qRKzvxN1muBFdougATrNw@mail.gmail.com' \
--to=gnachman@llamas.org \
--cc=emacs-devel@gnu.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.