unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: George Nachman <gnachman@llamas.org>
Cc: emacs-devel@gnu.org
Subject: Re: What capabilities do you wish terminal emulators would report?
Date: Fri, 08 May 2020 17:30:35 +0300	[thread overview]
Message-ID: <83blmyijn8.fsf@gnu.org> (raw)
In-Reply-To: <CAB5Rqom-yxMcAgiNo=F1-MjhxqNQ2qRKzvxN1muBFdougATrNw@mail.gmail.com> (message from George Nachman on Fri, 8 May 2020 00:34:27 -0700)

> From: George Nachman <gnachman@llamas.org>
> Date: Fri, 8 May 2020 00:34:27 -0700
> 
> 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?

Support for bidi reordering seems to be missing.

> 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

The "emacs" column seems to be empty, is that on purpose?



  parent reply	other threads:[~2020-05-08 14:30 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 [this message]
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

  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=83blmyijn8.fsf@gnu.org \
    --to=eliz@gnu.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 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).