From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 13:20:27 -0800 [thread overview]
Message-ID: <08c7660f-ee16-7159-581c-c8b2526a6035@gmail.com> (raw)
In-Reply-To: <831qcghn52.fsf@gnu.org>
On 11/23/2023 12:47 AM, Eli Zaretskii wrote:
> IMNSHO, it will be a sad day when different completion sources will
> present different completion UI. There will be no end to user
> confusion.
I think Spencer's suggestion below would be ok (assuming it actually
works). Then it's up to the users themselves to opt-in to different UI
for different sources:
On 11/22/2023 3:05 PM, Spencer Baugh wrote:
> - Maybe completion-category-overrides could change
> completion-in-region-function based on the category?
Whether that's the best solution is another story, but I don't think it
would cause any extra confusion, since nothing would change by default.
next prev parent reply other threads:[~2023-11-23 21:20 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
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 [this message]
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
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=08c7660f-ee16-7159-581c-c8b2526a6035@gmail.com \
--to=jporterbugs@gmail.com \
--cc=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 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).