From: Dmitry Gutov <dmitry@gutov.dev>
To: Spencer Baugh <sbaugh@janestreet.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Jim Porter <jporterbugs@gmail.com>,
me@eshelyaron.com, emacs-devel@gnu.org,
Juri Linkov <juri@linkov.net>
Subject: Re: Allowing completion sources to customize completion display
Date: Sat, 25 Nov 2023 02:25:21 +0200 [thread overview]
Message-ID: <7ac85e70-74cb-6a75-3188-9873ecd6b6ee@gutov.dev> (raw)
In-Reply-To: <ier1qcfkqm5.fsf@janestreet.com>
On 24/11/2023 19:28, Spencer Baugh wrote:
> But basing this on the source is totally wrong. Instead if I, as a
> user, think inline preview is better for multi-line completion
> candidates, then inline preview should be used for multi-line completion
> candidates regardless of where those candidates come from.
Are multi-line completions better shown inline? If I had to choose, I
might actually choose the opposite: show the shorter ones inline, and
the long ones in a separate buffer -- so that the current buffer's text
doesn't jump up and down as I'm typing something.
But that strongly depends on how those long completions are going to be
presented, whether they should replace the current text or just add new
one (multiple lines of it), whether they are allowed to vary a lot, etc.
next prev parent reply other threads:[~2023-11-25 0:25 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
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 [this message]
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=7ac85e70-74cb-6a75-3188-9873ecd6b6ee@gutov.dev \
--to=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=juri@linkov.net \
--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).