all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: jonas@bernoul.li, emacs-devel@gnu.org,
	philippe.vaucher@gmail.com, monnier@iro.umontreal.ca,
	adam@alphapapa.net, kyle@kyleam.com, drew.adams@oracle.com
Subject: Re: handling many matches
Date: Sat, 02 May 2020 09:29:28 +0300	[thread overview]
Message-ID: <837dxuvohj.fsf@gnu.org> (raw)
In-Reply-To: <d9f15b2a-d8b3-0c84-b7da-65aa30082e57@yandex.ru> (message from Dmitry Gutov on Sat, 2 May 2020 01:16:07 +0300)

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 2 May 2020 01:16:07 +0300
> 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>
> 
> 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.

IMNSHO, we should first develop the infrastructure for such "smart"
presentation of completion candidates and make it our default
completion strategy, and only after that consider changes, like the
proposed "namespacing" of APIs, that will allow users to use
completion as a substitute for Help commands.  It is IMO a bad idea to
flood the completion lists with many dozens of candidates and force
users to wade through them.  I certainly wouldn't call that "progress"
for Emacs.



  parent reply	other threads:[~2020-05-02  6:29 UTC|newest]

Thread overview: 19+ 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
2020-05-01 22:47   ` Drew Adams
2020-05-02  6:29   ` Eli Zaretskii [this message]
2020-05-02 13:26     ` handling many matches 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
     [not found] <<119c0543-387d-4fad-b7fe-b4e07a7be4f8@default>
     [not found] ` <<d9f15b2a-d8b3-0c84-b7da-65aa30082e57@yandex.ru>
     [not found]   ` <<837dxuvohj.fsf@gnu.org>
     [not found]     ` <<f56f84c9-80ac-18f0-35fb-49034122853e@yandex.ru>
     [not found]       ` <<83wo5usaui.fsf@gnu.org>
2020-05-02 18:21         ` Drew Adams
2020-05-02 18:34           ` Eli Zaretskii
     [not found]         ` <<14f6ff0f-afcc-5cc2-b8ce-491209c1e739@yandex.ru>
     [not found]           ` <<83y2qaqoxi.fsf@gnu.org>
     [not found]             ` <<5f531674-88b2-55fd-a677-7cbd57a62b91@yandex.ru>
     [not found]               ` <<83tv0yqmeq.fsf@gnu.org>
     [not found]                 ` <<e8e5136a-129b-0588-1e2d-74a9950899be@yandex.ru>
     [not found]                   ` <<83pnbmqjcz.fsf@gnu.org>
     [not found]                     ` <<beb7562b-f05c-0f8c-64ca-f6ce78f4d779@yandex.ru>
     [not found]                       ` <<83imheqin8.fsf@gnu.org>
2020-05-02 19:51                         ` Drew Adams
     [not found] <<<119c0543-387d-4fad-b7fe-b4e07a7be4f8@default>
     [not found] ` <<<d9f15b2a-d8b3-0c84-b7da-65aa30082e57@yandex.ru>
     [not found]   ` <<<837dxuvohj.fsf@gnu.org>
     [not found]     ` <<<f56f84c9-80ac-18f0-35fb-49034122853e@yandex.ru>
     [not found]       ` <<<83wo5usaui.fsf@gnu.org>
     [not found]         ` <<db6f7655-0562-4eb1-a8a2-52f194f44471@default>
     [not found]           ` <<83o8r6qj8a.fsf@gnu.org>
2020-05-02 19:18             ` Drew Adams

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=837dxuvohj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=dgutov@yandex.ru \
    --cc=drew.adams@oracle.com \
    --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.