From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41732@debbugs.gnu.org, Fredrik Salomonsson <plattfot@gmail.com>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: bug#41732: issue with emacs-lua-mode and emacs-next
Date: Wed, 17 Jun 2020 00:34:23 -0400 [thread overview]
Message-ID: <87zh92e2eo.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ1-=iodmfNCmxxW_W621s-H8zFc5PRViHcs6nOY14qPMg@mail.gmail.com> (zimoun's message of "Sun, 7 Jun 2020 11:31:41 +0200")
Hello Simon!
Sorry for my delayed answer.
zimoun <zimon.toutoune@gmail.com> writes:
> Dear Maxim,
>
> On Sun, 7 Jun 2020 at 06:39, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> Some people have been adding emacs-next-something packages (IIRC); I
>> think it's OK for the big, complicated packages that need effort to
>> port, but otherwise I wouldn't like seeing this happening for all
>> packages.
>
> I agree. I am not suggesting to duplicate all the packages with
> 'emacs-next-something'. There is already enough to do with the
> current ones. :-)
>
>
>> > Well, I am not suggesting to duplicate all the Emacs packages with
>> > something like 'emacs-next-<package>' because it is too much. I am
>> > suggesting to provide 'package-with-emacs-next' and then for example
>> > in my manifest file I would use this new procedure to generate
>> > on-the-fly these next packages; as an expert Emacs mode.
>>
>> That sounds like a good idea; provide a way for users to rewrite their
>> package at the level of their manifest file (which is already possible
>> IIUC).
>
> I propose to provide 'package-with-emacs-next' for the people in the
> experimental mood. :-) For example, the manifest looks like:
>
> (use-modules (guix build-system emacs)
> (gnu packages emacs)
> (gnu packages emacs-xyz))
>
> (packages->manifest
> (cons emacs-next
> (map
> package-with-emacs-next
> (list
> emacs-lua-mode
> emacs-magit))))
>
> Then the expert uses it with:
>
> guix package -m manifest.scm
>
> Well, the attached patch does that. And maybe, an entry to the
> Cookbook could be worth.
That's really nice! Thank you for providing it. I've tried it in my
manifest, by stitching a couple manifests objects together
`concatenate-manifests' like so:
--8<---------------cut here---------------start------------->8---
(concatenate-manifests
(list
;;; Emacs packages.
(packages->manifest
(cons emacs-next
(map package-with-emacs-next
(map specification->package
'("emacs-auctex"
"emacs-bash-completion"
[...]
"emacs-yasnippet"
"emacs-yasnippet-snippets")))))
;; Other software.
(specifications->manifest
'("adb"
[...]
"arc-icon-theme"
"arc-theme"
...))))
--8<---------------cut here---------------end--------------->8---
And after a couple fixes on master, I was able to build my profile with
my Emacs packages collection built against Emacs 27! I'm now having
some issues due to the apparent renaming of the generated autoload
files. I haven't had the time to look for a fix yet. It breaks at
least Helm (and probably others), as it cannot find its own autoload
file.
next-helm-autoloads.el ->
/gnu/store/fnwalhxi94fhr8h2dfg602zd9plarwx0-emacs-next-helm-3.6.2/share/emacs/site-lisp/next-helm-autoloads.el
(instead of helm-autoloads.el)
> Note that 'package-with-explicite-emacs' and
> 'package-with-explicit-python' should be refactored, another story.
> :-)
I wholly agree! It seems these have much in common. Perhaps (guix
packages) could be a new home for the factored out bits.
To be continued!
Maxim
next prev parent reply other threads:[~2020-06-17 4:35 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 [this message]
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
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=87zh92e2eo.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=41732@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=plattfot@gmail.com \
--cc=zimon.toutoune@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).