unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 41732@debbugs.gnu.org, Fredrik Salomonsson <plattfot@gmail.com>
Subject: bug#41732: issue with emacs-lua-mode and emacs-next
Date: Sat, 6 Jun 2020 17:30:11 +0200	[thread overview]
Message-ID: <CAJ3okZ3JoFb3T_f=bnLxNxGnD1FDcxzoODP29+5bi9MT-K7Jrw@mail.gmail.com> (raw)
In-Reply-To: <87sgf8ffj9.fsf@nicolasgoaziou.fr>

Dear Nicolas,

On Sat, 6 Jun 2020 at 16:13, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:

> > Somehow, one needs to change the Emacs version used by the Emacs
> > toolchain to bytecompile, right?
> > I do not know if it makes sense, but we could add something like
> > 'package-with-emacs-next' similar to 'package-with-python2' or
> > 'package-with-ocam4.07'.
> > WDYT?
>
> This sounds like serious overhead for a single package. Maybe we could
> try to prevent byte-compilation for the package and see what happens?

Maybe I miss the issue.  From my understanding, all the Emacs packages
are byte-compiled with the current Emacs.  Therefore, "guix install
emacs-next emacs-foo" and then "M-x foo" works by luck -- well because
the Emacs VM is stable. :-)
And I do not know how to rebuild all my Emacs packages using
'emacs-next' instead of the current Emacs.  Maybe I miss something.

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.

I do not know if this proposal makes sense.  Probably not. :-)
(My regular Emacs is the current version and I very rarely use
emacs-next because I started Emacs with 23 therefore 24 was already a
so-nice improvement. :-))

All the best,
simon




  reply	other threads:[~2020-06-06 15:31 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 [this message]
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
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='CAJ3okZ3JoFb3T_f=bnLxNxGnD1FDcxzoODP29+5bi9MT-K7Jrw@mail.gmail.com' \
    --to=zimon.toutoune@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).