From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: me@eshelyaron.com, sbaugh@janestreet.com, emacs-devel@gnu.org
Subject: Re: Allowing completion sources to customize completion display
Date: Thu, 23 Nov 2023 16:35:49 +0200 [thread overview]
Message-ID: <83v89sfsfu.fsf@gnu.org> (raw)
In-Reply-To: <87zfz4in31.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Thu, 23 Nov 2023 14:03:37 +0000 (UTC)
> Cc: me@eshelyaron.com, sbaugh@janestreet.com, emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
> >> From: sbaugh@catern.com
> >> Date: Thu, 23 Nov 2023 12:38:22 +0000 (UTC)
> >> Cc: Eshel Yaron <me@eshelyaron.com>, sbaugh@janestreet.com,
> >> emacs-devel@gnu.org
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> >
> >> > 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.
> >>
> >> Sure. I, as a user, want to specify two different UIs for two different
> >> completion sources.
> >>
> >> Currently this is impossible.
> >
> > It shouldn't be possible. Users should not need to be aware of the
> > completion sources.
>
> Why not? I just explained a use case where users are definitely already
> aware of the completion sources, and Eshel mentioned another one.
You _can_ be aware of the source, but we must not _require_ users to
be aware. If the user is NOT aware, he/she will not be able to set up
the UI according to the source.
next prev parent reply other threads:[~2023-11-23 14:35 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 [this message]
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=83v89sfsfu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.com \
--cc=sbaugh@catern.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.