From: Xinglu Chen <public@yoctocell.xyz>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 48237@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#48237] [PATCH] gnu: emacs-consult: Add ‘emacs-ve
Date: Fri, 07 May 2021 16:23:46 +0200 [thread overview]
Message-ID: <87k0oa4o7h.fsf@yoctocell.xyz> (raw)
In-Reply-To: <ae577b203f68d766d7dc8b89c3dd2ac5067c192d.camel@student.tugraz.at>
On Wed, May 05 2021, Leo Prikler wrote:
> Am Mittwoch, den 05.05.2021, 15:26 +0200 schrieb Xinglu Chen:
>> emacs-vertico is an optional dependency so maybe there is a better
>> way
>> deal with this. Splitting the package into multiple outputs might be
>> a
>> better idea, but I don’t know how we would do that.
> This is certainly an interesting question. With other Emacs packages,
> there is sometimes a contrib version, that adds "more", see e.g. org-
> mode or telega. But those are tied closely to what upstream considers
> contrib, so I don't think that applies here.
Yeah, Org has a separate contrib/ directory.
> IIUC selectrum is likewise optional. Perhaps we should consider not
> propagating optional inputs, but rather adding them as normal inputs –
> so that byte compilation succeeds, but users won't be forced to have a
> rather large elisp library as part of their profiles if it's not
> needed.
I think this might be the best option.
next prev parent reply other threads:[~2021-05-07 14:24 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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0oa4o7h.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=48237@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=maxim.cournoyer@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/guix.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).