From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jonas Bernoulli <jonas@bernoul.li>,
Emacs developers <emacs-devel@gnu.org>,
Philippe Vaucher <philippe.vaucher@gmail.com>,
Adam Porter <adam@alphapapa.net>, Kyle Meyer <kyle@kyleam.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: handling many matches [was: [ELPA] New package: transient]
Date: Sat, 2 May 2020 01:16:07 +0300 [thread overview]
Message-ID: <d9f15b2a-d8b3-0c84-b7da-65aa30082e57@yandex.ru> (raw)
In-Reply-To: <119c0543-387d-4fad-b7fe-b4e07a7be4f8@default>
On 01.05.2020 20:20, Drew Adams wrote:
> 1. Progressive matching, i.e., narrowing the set
> of candidates by matching another pattern.
> (Rinse and repeat.)
>
> 2. Pruning, by excluding matches.
>
> 3. On-demand help on individual candidates.
This is all high-maintenance. It requires the user to master the
matching interface first, with extra keys and new behaviors.
Whereas "other editors" have already solved this better (perhaps not
ideally, but better) by doing fuzzy matching with smart enough sorting.
We should start by matching that functionality, and only then add extra
capabilities, maybe.
next prev parent reply other threads:[~2020-05-01 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:20 handling many matches [was: [ELPA] New package: transient] Drew Adams
2020-05-01 22:16 ` Dmitry Gutov [this message]
2020-05-01 22:47 ` Drew Adams
2020-05-02 6:29 ` handling many matches Eli Zaretskii
2020-05-02 13:26 ` Dmitry Gutov
2020-05-02 13:52 ` Eli Zaretskii
2020-05-02 16:13 ` Dmitry Gutov
2020-05-02 16:31 ` Eli Zaretskii
2020-05-02 16:58 ` Dmitry Gutov
2020-05-02 17:25 ` Eli Zaretskii
2020-05-02 18:17 ` Dmitry Gutov
2020-05-02 18:31 ` Eli Zaretskii
2020-05-02 18:39 ` Dmitry Gutov
2020-05-02 18:46 ` Eli Zaretskii
2020-05-02 21:11 ` Dmitry Gutov
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=d9f15b2a-d8b3-0c84-b7da-65aa30082e57@yandex.ru \
--to=dgutov@yandex.ru \
--cc=adam@alphapapa.net \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=kyle@kyleam.com \
--cc=monnier@iro.umontreal.ca \
--cc=philippe.vaucher@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 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.