From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 41732@debbugs.gnu.org, Fredrik Salomonsson <plattfot@gmail.com>
Subject: bug#41732: New ’package-with-emacs-next’ procedure
Date: Sun, 27 Sep 2020 23:03:40 -0400 [thread overview]
Message-ID: <878scur4ab.fsf@gmail.com> (raw)
In-Reply-To: <877dsf61ch.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 27 Sep 2020 11:00:30 +0200")
Hello,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Possibly. And then Magit uses emacs-no-x as an input, so we may need to
> also add --with-input=emacs-no-x=emacs-next to the command.
>
> I'm just pointing out that the process is not as straightforward as it
> might seem. So, it doesn't sound right to simply suggest
>
> guix build -m manifest.scm --with-input=emacs-minimal=emacs-next
>
> in the manual/cookbook without caution.
>
> Or maybe `package-with-emacs-next' could be more high-level, and handle
> all of these cases. I don't know.
Yeah, that would probably me more convenient/robust to use, if it was
covering for all the weird cases one might forget. I'd still be in
favor of having such a helper procedure.
Maxim
next prev parent reply other threads:[~2020-09-28 3:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 3:14 bug#41732: issue with emacs-lua-mode and emacs-next Fredrik Salomonsson
2020-06-06 3:17 ` Fredrik Salomonsson via web
2020-06-06 8:10 ` Nicolas Goaziou
2020-06-06 10:26 ` zimoun
2020-06-06 14:13 ` Nicolas Goaziou
2020-06-06 15:30 ` zimoun
2020-06-07 4:39 ` Maxim Cournoyer
2020-06-07 9:31 ` zimoun
2020-06-17 4:34 ` Maxim Cournoyer
2020-09-16 14:51 ` bug#41732: New ’package-with-emacs-next’ procedure zimoun
2020-09-26 16:12 ` zimoun
2020-09-26 16:53 ` Nicolas Goaziou
2020-09-27 3:45 ` Maxim Cournoyer
2020-09-27 9:00 ` Nicolas Goaziou
2020-09-28 3:03 ` Maxim Cournoyer [this message]
2020-09-28 8:29 ` zimoun
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=878scur4ab.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=41732@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=plattfot@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).