From: Arun Isaac <arunisaac@systemreboot.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Xinglu Chen <public@yoctocell.xyz>
Cc: 48237@debbugs.gnu.org
Subject: [bug#48237] [PATCH] gnu: emacs-consult: Add ‘emacs-ve
Date: Tue, 07 Sep 2021 02:04:22 +0530 [thread overview]
Message-ID: <87ilzdl9yp.fsf@systemreboot.net> (raw)
In-Reply-To: <fd28931b2c8a997621958bed77802cc9ef24822c.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Hi all,
> unless you're already using autocomplete or company and
> thus have them in your manifest, you probably don't want them to be
> installed by emacs-foo. Does this make sense?
I agree. Closure size isn't the right metric for this
case. emacs-vertico and emacs-selectrum aren't really optional
dependencies in the normal sense. The user would only want one of them
in their profile, and never both. Propagating both would rather be a
nuisance to the user.
> I would prefer not go that route (variants multiplication), especially
> when the user already has a way to customize.
I agree. Variant multiplication would result in a minor combinatorial
explosion. emacs-vertico and emacs-selectrum are anyway the kind of
package a user would explicitly install in their profile.
Cheers!
Arun
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
next prev parent reply other threads:[~2021-09-06 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 13:26 [bug#48237] [PATCH] gnu: emacs-consult: Add ‘emacs-ve Xinglu Chen
2021-05-05 17:39 ` Leo Prikler
2021-05-07 14:23 ` Xinglu Chen
2021-06-02 15:32 ` Xinglu Chen
2021-08-11 15:23 ` Arun Isaac
2021-09-06 13:47 ` Xinglu Chen
2021-09-06 17:51 ` Maxim Cournoyer
2021-09-06 18:05 ` Liliana Marie Prikler
2021-09-06 20:34 ` Arun Isaac [this message]
2021-09-06 23:18 ` Maxim Cournoyer
2021-09-06 23:17 ` Maxim Cournoyer
2021-09-07 7:05 ` Liliana Marie Prikler
2021-09-07 17:49 ` Xinglu Chen
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=87ilzdl9yp.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=48237@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=public@yoctocell.xyz \
/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/guix.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.