From: Eshel Yaron <me@eshelyaron.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Inline completion preview
Date: Fri, 27 Oct 2023 17:53:23 +0200 [thread overview]
Message-ID: <m1zg04qcy4.fsf@eshelyaron.com> (raw)
In-Reply-To: <87zg04cuh2.fsf@localhost> (Ihor Radchenko's message of "Fri, 27 Oct 2023 08:58:33 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Eshel Yaron <me@eshelyaron.com> writes:
>
>> Sorry, that might have not been clear enough, I wrote:
>>
>> ISTM that the best approach is a simple library that uses only
>> `completion-at-point` as a backend, because `completion-at-point` is
>> already extensible enough to support a variety of completion
>> backends.
>>
>> None of the aforementioned packages take that approach, so I wrote
>> `completion-preview.el` do demonstrate and test this approach. As to
>> the question of adding this feature to core, since it's quite a simple
>> and useful addition, I just think it could be nice to have it OOTB.
>>
>
> Don't corfu do it already?
No, this is a somewhat different feature,
> From https://github.com/minad/corfu:
>
> Corfu is a small package, which relies on the Emacs completion
> facilities and concentrates on providing a polished completion UI.
Indeed `corfu` provides a completion UI, but not an inline completion preview.
`corfu`'s completion UI replaces the *Completions* buffer for
in-buffer completions. Completion preview is something related but
independent from the completion UI. Namely a suggestion for a single
completion candidate that automatically shows up after point as you
type. It appears inline, as if you've already inserted that candidate,
in that sense it gives you a preview for the completion operation.
The package `corfu-candidate-overlay` is another project that does
provide completion preview and builds on top of `corfu` instead of
`completion-at-point` directly.
next prev parent reply other threads:[~2023-10-27 15:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:11 Inline completion preview Eshel Yaron
2023-10-26 18:38 ` Eli Zaretskii
2023-10-26 19:39 ` Eshel Yaron
2023-10-27 5:52 ` Eli Zaretskii
2023-10-27 15:43 ` Eshel Yaron
2023-10-27 17:12 ` Eli Zaretskii
2023-10-27 18:13 ` Eshel Yaron
2023-10-27 20:25 ` chad
2023-10-28 16:47 ` Juri Linkov
2023-10-28 19:01 ` Eshel Yaron
2023-10-29 16:24 ` Alexander Adolf
2023-10-29 23:29 ` João Távora
2023-10-30 9:25 ` Juergen Fenn
2023-10-30 9:36 ` João Távora
2023-10-30 11:04 ` Dmitry Gutov
2023-10-30 12:42 ` Alexander Adolf
2023-10-30 13:01 ` João Távora
2023-10-30 17:32 ` Alexander Adolf
2023-10-30 17:52 ` João Távora
2023-10-30 13:20 ` Dmitry Gutov
2023-10-30 17:43 ` Alexander Adolf
2023-10-30 22:49 ` Dmitry Gutov
2023-10-31 6:50 ` Eshel Yaron
2023-10-31 17:31 ` Alexander Adolf
2023-10-31 17:43 ` Eshel Yaron
2023-10-31 23:29 ` Dmitry Gutov
2023-11-01 8:30 ` Eshel Yaron
2023-11-01 10:11 ` João Távora
2023-11-01 10:44 ` Eshel Yaron
2023-11-01 11:07 ` João Távora
2023-11-01 12:17 ` Eshel Yaron
2023-11-01 12:23 ` Dmitry Gutov
2023-11-01 14:07 ` Juergen Fenn
2023-11-01 19:57 ` Dmitry Gutov
2023-11-01 12:08 ` Dmitry Gutov
2023-11-01 12:14 ` Dmitry Gutov
2023-11-01 12:24 ` Dmitry Gutov
2023-11-01 12:29 ` Eshel Yaron
2023-11-01 12:32 ` Dmitry Gutov
2023-11-01 12:34 ` Eli Zaretskii
2023-11-01 12:36 ` Dmitry Gutov
2023-11-01 13:28 ` Po Lu
2023-11-01 19:49 ` Dmitry Gutov
2023-10-27 8:58 ` Ihor Radchenko
2023-10-27 15:53 ` Eshel Yaron [this message]
2023-10-27 11:49 ` João Távora
2023-10-27 11:52 ` João Távora
2023-10-27 12:18 ` Eli Zaretskii
2023-10-27 12:55 ` João Távora
2023-10-27 12:58 ` Eli Zaretskii
2023-10-27 13:05 ` 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=m1zg04qcy4.fsf@eshelyaron.com \
--to=me@eshelyaron.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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.