From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: thibaut.verron@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Standardizing more key bindings?
Date: Tue, 06 Oct 2020 10:43:24 -0400 [thread overview]
Message-ID: <jwvsgarv35y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8c05eb11-102d-4d94-21ba-b60ceb6d9c43@gmail.com> (Nikolay Kudryavtsev's message of "Tue, 6 Oct 2020 17:24:14 +0300")
> So one decent example I have is minibuffer completion. Lets say I'm using
> ErgoEmacs and it expects previous element to work on F11 and next element on
> F12. But there are multiple minibuffer completion packages, like Ivy,
> Icicles, Helm and ErgoEmacs developers have to currently try to provide
> concrete bindings for whatever they choose to support.
The problem with it is that all of those completion packages provide
a slightly different set of commands. So while the "next element" and
"previous element" command can easily be handled such that the choice of
key is handled elsewhere, you're still stuck with the choice of key for
the commands specific to Helm (say), unless your protocol covers "a
superset of all the completion packages". If it's not a superset, then
the few missing commands will end up sticking out like a sore thumb
(or even conflict with some other keybinding).
So, I think the "keytheme" packages should be able to do more than give
explicit bindings to a particular set of (concrete or abstract)
commands. They should also be able to describe their style in a more
"intensional" way, which would be used to *compute* the key to use for
a new command based on some suggestion from the command's package.
Stefan
next prev parent reply other threads:[~2020-10-06 14:43 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 9:31 Standardizing more key bindings? Thibaut Verron
2020-09-27 15:57 ` Stefan Monnier
2020-09-28 3:44 ` Richard Stallman
2020-09-28 4:38 ` Thibaut Verron
2020-09-28 7:39 ` Thibaut Verron
2020-09-29 3:30 ` Richard Stallman
2020-09-29 5:07 ` Thibaut Verron
2020-09-29 10:36 ` Vasilij Schneidermann
2020-10-01 4:09 ` Richard Stallman
2020-10-01 5:20 ` Thibaut Verron
2020-09-29 21:56 ` Dmitry Gutov
2020-11-01 4:27 ` Richard Stallman
2020-11-01 6:56 ` References to "REPL" from past Jean Louis
2020-11-01 13:51 ` Standardizing more key bindings? Stefan Monnier
2020-11-02 5:41 ` Richard Stallman
2020-11-02 6:14 ` Yuri Khan
2020-11-02 8:08 ` tomas
2020-11-02 9:50 ` Dmitry Gutov
2020-11-02 11:40 ` Python REPL using standard library functions Yuri Khan
2020-11-02 22:46 ` Dmitry Gutov
2020-11-01 21:35 ` Standardizing more key bindings? Dmitry Gutov
2020-11-01 22:27 ` Drew Adams
2020-11-02 5:46 ` Richard Stallman
2020-09-29 21:58 ` Dmitry Gutov
2020-09-30 6:08 ` Thibaut Verron
2020-09-30 16:58 ` Opening Up More Keymaps " T.V Raman
2020-09-30 17:29 ` Thibaut Verron
2020-09-30 18:12 ` Robert Pluim
2020-09-30 18:16 ` Stefan Monnier
2020-09-30 18:35 ` T.V Raman
2020-09-30 18:41 ` Robert Pluim
2020-09-30 19:54 ` Stefan Monnier
2020-09-30 19:58 ` T.V Raman
2020-09-30 20:00 ` Noam Postavsky
2020-09-30 20:03 ` T.V Raman
2020-09-30 21:00 ` chad
2020-09-30 21:34 ` T.V Raman
2020-09-30 20:45 ` Stefan Monnier
2020-09-30 20:51 ` T.V Raman
2020-09-30 21:13 ` Gregory Heytings via Emacs development discussions.
2020-09-30 21:19 ` Stefan Monnier
2020-09-30 21:37 ` T.V Raman
2020-09-30 21:44 ` Stefan Monnier
2020-09-30 23:07 ` T.V Raman
2020-10-01 2:35 ` Eli Zaretskii
2020-10-01 3:27 ` Stefan Monnier
2020-10-01 12:38 ` Ergus
2020-10-01 14:17 ` Stefan Kangas
2020-10-01 14:45 ` Caio Henrique
2020-10-02 3:54 ` Richard Stallman
2020-10-02 10:43 ` Ergus
2020-10-04 19:34 ` Juri Linkov
2020-10-02 3:49 ` Richard Stallman
2020-10-02 6:56 ` Eli Zaretskii
2020-10-02 11:34 ` Ergus
2020-10-02 12:26 ` Eli Zaretskii
2020-10-04 3:38 ` Richard Stallman
2020-10-04 10:38 ` Thibaut Verron
2020-10-04 13:46 ` Alfred M. Szmidt
2020-10-04 16:24 ` Thibaut Verron
2020-10-04 17:00 ` Alfred M. Szmidt
2020-10-04 17:32 ` Thibaut Verron
2020-10-04 17:46 ` Alfred M. Szmidt
2020-10-05 3:11 ` Richard Stallman
2020-10-06 8:59 ` Lars Brinkhoff
2020-10-04 17:46 ` Alfred M. Szmidt
2020-10-05 3:13 ` Richard Stallman
2020-10-04 14:10 ` Howard Melman
2020-10-02 3:45 ` Richard Stallman
2020-10-02 6:26 ` Thibaut Verron
2020-10-04 3:39 ` Richard Stallman
2020-10-04 3:39 ` Richard Stallman
2020-10-02 6:52 ` Eli Zaretskii
2020-10-02 14:00 ` Stefan Monnier
2020-10-04 3:38 ` Richard Stallman
2020-10-04 7:16 ` Eli Zaretskii
2020-10-05 3:14 ` Richard Stallman
2020-10-02 13:56 ` Stefan Monnier
2020-10-03 2:57 ` Richard Stallman
2020-10-06 12:53 ` Nikolay Kudryavtsev
2020-10-06 13:27 ` Stefan Monnier
2020-10-06 14:24 ` Nikolay Kudryavtsev
2020-10-06 14:43 ` Stefan Monnier [this message]
2020-10-08 9:40 ` Nikolay Kudryavtsev
2020-10-07 4:19 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2020-09-27 21:38 yarnton--- via Emacs development discussions.
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=jwvsgarv35y.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=nikolay.kudryavtsev@gmail.com \
--cc=thibaut.verron@gmail.com \
/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).