From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@catern.com, emacs-devel@gnu.org
Subject: Re: Allowing completion sources to customize completion display
Date: Sat, 25 Nov 2023 21:08:20 +0200 [thread overview]
Message-ID: <fd7d98ac-3f95-e0df-c44c-23ef7c764cc7@gutov.dev> (raw)
In-Reply-To: <83o7fhbqj7.fsf@gnu.org>
On 25/11/2023 21:07, Eli Zaretskii wrote:
>> Date: Sat, 25 Nov 2023 20:27:51 +0200
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>> I hadn't considered company-mode in that context, but the preview
>> frontend in there should look more or less like the "Completion Preview"
>> feature proposed (or recently added?) to the core.
> It is possible that providing an in-buffer preview for multi-line
> completions makes no sense, and we shouldn't even try. If the
> solutions are to show the preview in a separate window, then how is
> this different from popping up the*Completions* buffer?
I think when we say "preview", we usually mean "inline preview". Not
separate window.
next prev parent reply other threads:[~2023-11-25 19:08 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
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 [this message]
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=fd7d98ac-3f95-e0df-c44c-23ef7c764cc7@gutov.dev \
--to=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sbaugh@catern.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).