From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: North Year <ny-ml@outlook.com>, Visuwesh <visuweshm@gmail.com>,
Okamsn <okamsn@protonmail.com>,
emacs-devel@gnu.org
Subject: Re: Adding the `prescient` packages to NonGNU ELPA?
Date: Fri, 16 Dec 2022 22:28:22 -0500 [thread overview]
Message-ID: <jwvwn6q1zgg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pmcj2lsg.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 16 Dec 2022 19:25:35 +0000")
>> 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.
>
> This has already been discussed in the thread, and it appears the head
> maintainer is opposed to this approach. I think it is a pity, as you
> say it usually is not problem to add optional support for a package that
> may or may not be installed (bbdb is another example that does this well).
Is there anything that would prevent us from packaging all the files in
a single tarball?
Stefan
next prev parent reply other threads:[~2022-12-17 3:28 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
2022-12-16 19:25 ` Philip Kaludercic
2022-12-17 3:28 ` Stefan Monnier [this message]
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=jwvwn6q1zgg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ny-ml@outlook.com \
--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).