From: North Year <ny-ml@outlook.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
Okamsn <okamsn@protonmail.com>,
emacs-devel@gnu.org
Subject: Re: Adding the `prescient` packages to NonGNU ELPA?
Date: Fri, 16 Dec 2022 04:41:06 -0500 [thread overview]
Message-ID: <MW4PR14MB53273CFA44C8E3CDF465EE37E7E69@MW4PR14MB5327.namprd14.prod.outlook.com> (raw)
In-Reply-To: <874jutft6g.fsf@gmail.com>
On 11/20/22 22:40, Visuwesh wrote:
>>>
>>> - `company-prescient`: Use `prescient` sorting with Company
>>>
>>> - `corfu-prescient`: Use `prescient` sorting and filtering with Corfu
>>>
>>> - `vertico-prescient`: Use `prescient` sorting and filtering with Vertico
>>
>> Could you explain the need for these other packages? If we are talking
>> about a completion style, why do other packages require their own
>> support?
>
>AFAIU, it is because there is no common way to call a function after
>ending a completing-read and/or completion-in-region call so we end up
>needing a UI specific way to do so. The function records the selected
>candidate, necessary for fuzzy(?) matching based on frequency and
>recency ("frecency").
>The README does a better job at explaining this than I do here (which is
>based on understanding on how the package worked before it underwent
>extensive rewrite).
Why `prescient`, `company-prescient`, `corfu-prescient`,
`vertico-prescient` need to be separate packages? Can't they bundle
together as a single package? Eglot has additional support for company
despite that company isn't a builtin package yet, and eglot doesn't have
a `company-eglot` additional package.
next prev parent reply other threads:[~2022-12-16 9:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 3:27 Adding the `prescient` packages to NonGNU ELPA? Okamsn
2022-11-20 9:24 ` Philip Kaludercic
2022-11-20 11:23 ` Stefan Kangas
2022-11-20 15:19 ` Stefan Monnier
2022-11-20 15:41 ` Philip Kaludercic
2022-11-21 21:17 ` Richard Stallman
2022-11-22 13:53 ` Akib Azmain Turja
2022-11-23 23:12 ` okamsn
2022-11-26 0:50 ` Richard Stallman
2022-11-20 17:10 ` Visuwesh
2022-11-20 18:39 ` Stefan Monnier
2022-12-16 9:41 ` North Year [this message]
2022-12-16 19:25 ` Philip Kaludercic
2022-12-17 3:28 ` Stefan Monnier
2022-12-17 9:17 ` Philip Kaludercic
2022-12-17 15:52 ` Stefan Monnier
2022-12-17 16:07 ` Philip Kaludercic
2022-12-17 16:24 ` Philip Kaludercic
2022-12-17 18:01 ` Okamsn
2022-12-17 18:08 ` Philip Kaludercic
2022-12-17 18:39 ` Stefan Monnier
2022-12-20 1:32 ` Okamsn
2022-12-20 3:10 ` Stefan Monnier
2022-11-20 17:42 ` Okamsn
2022-12-05 0:27 ` Okamsn
2022-12-05 15:21 ` Stefan Monnier
2022-12-09 3:58 ` Okamsn
2022-12-09 15:08 ` Stefan Monnier
2022-12-09 15:27 ` Philip Kaludercic
2022-12-10 4:10 ` Richard Kim
2022-12-10 15:12 ` Stefan Monnier
2022-12-10 16:38 ` Richard Kim
2022-12-10 17:44 ` Stefan Monnier
2022-12-05 17:21 ` Philip Kaludercic
2022-12-16 2:04 ` Okamsn
2022-12-16 19:26 ` Philip Kaludercic
2022-11-22 15:41 ` Jonas Bernoulli
2022-11-22 21:09 ` Stefan Monnier
2022-11-23 9:56 ` Jonas Bernoulli
2022-11-23 12:33 ` Stefan Monnier
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=MW4PR14MB53273CFA44C8E3CDF465EE37E7E69@MW4PR14MB5327.namprd14.prod.outlook.com \
--to=ny-ml@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=okamsn@protonmail.com \
--cc=philipk@posteo.net \
--cc=visuweshm@gmail.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).