From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: sbaugh@janestreet.com, emacs-devel@gnu.org
Subject: Re: Allowing completion sources to customize completion display
Date: Thu, 23 Nov 2023 10:47:21 +0200 [thread overview]
Message-ID: <831qcghn52.fsf@gnu.org> (raw)
In-Reply-To: <m1ttpcc1w0.fsf@dazzs-mbp.home> (message from Eshel Yaron on Thu, 23 Nov 2023 09:25:19 +0100)
> From: Eshel Yaron <me@eshelyaron.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 23 Nov 2023 09:25:19 +0100
>
> How about something like the following? That seems simple enough and
> gives individual capfs full discretion to specify their selection UI.
IMNSHO, it will be a sad day when different completion sources will
present different completion UI. There will be no end to user
confusion.
Completion UI is a user preference, and if we want to support
different UIs (as we already do), we should leave it to the user to
specify the UI he/she prefers, and then abide by that.
Completion-related frameworks that cannot work like that should not
pretend being "completion", but some different features, even if they
use completion functions under the hood.
next prev parent reply other threads:[~2023-11-23 8:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 23:05 Allowing completion sources to customize completion display Spencer Baugh
2023-11-23 8:25 ` Eshel Yaron
2023-11-23 8:47 ` Eli Zaretskii [this message]
2023-11-23 12:38 ` sbaugh
2023-11-23 13:48 ` Eli Zaretskii
2023-11-23 14:03 ` sbaugh
2023-11-23 14:35 ` Eli Zaretskii
2023-11-23 21:20 ` Jim Porter
2023-11-24 7:15 ` Eli Zaretskii
2023-11-24 17:28 ` Spencer Baugh
2023-11-24 20:52 ` [External] : " Drew Adams
2023-11-25 0:25 ` Dmitry Gutov
2023-11-25 17:36 ` sbaugh
2023-11-25 18:27 ` Dmitry Gutov
2023-11-25 19:07 ` Eli Zaretskii
2023-11-25 19:08 ` Dmitry Gutov
2023-11-25 20:04 ` Eli Zaretskii
2023-11-25 6:59 ` Eli Zaretskii
2023-11-23 14:44 ` 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=831qcghn52.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.com \
--cc=sbaugh@janestreet.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.