unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
	"Thompson, David" <dthompson2@worcester.edu>
Cc: 57878@debbugs.gnu.org
Subject: bug#57878: Minimal reproducible setup
Date: Wed, 12 Oct 2022 21:42:57 +0200	[thread overview]
Message-ID: <6873fe86a05a548e7427d2de7df04a27a967713a.camel@gmail.com> (raw)
In-Reply-To: <m17d1iskc0.fsf@fastmail.net>

Am Sonntag, dem 02.10.2022 um 10:25 +0200 schrieb Konrad Hinsen:
> As for Liliana's idea of disabling deferred compilation : shouldn't
> it be sufficient to have all Emacs Lisp packages in Guix AOT-
> compiled?
From personal experience, no.  Even if you compile code ahead of time,
there seem to be some leftovers that are deferred.  guix-emacs.el is an
oversight, but apart from that I also other leftovers (possibly from
init.el?)

> There would be nothing left to compile in deferred mode. A quick scan
> of the relevant page on Emacs Wiki
> (https://www.emacswiki.org/emacs/GccEmacs) suggests that some package
> manager do this.
In Guix, this is more or less a user choice – we advertised the
transformation by which you can opt-in to AOT compilation in a news
entry.  Also, enforcing ahead-of-time compilation does not fix the more
pressing issue of packages breaking with native compilation ;)

To quote Eli:
> More generally, we never expected people who have Emacs with native
> compilation available to want to disable it.  It made no sense to us
> during development of Emacs 28, and frankly, it still doesn't, at
> least to me.
I think this reasoning really falls flat in presence of any non-Emacs
package manager.  Like, obviously wanting to natively compile packages
managed by (dpkg, rpm, pacman, emerge, guix), but not natively
compiling a random elisp script you just downloaded from the web is a
legitimate use case.

Cheers




  reply	other threads:[~2022-10-12 19:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17  9:09 bug#57878: Emacs native compilation on startup can crash the system Konrad Hinsen
2022-09-17 10:28 ` bug#57878: Minimal reproducible setup Konrad Hinsen
2022-09-17 15:45   ` Konrad Hinsen
2022-09-17 23:19     ` Liliana Marie Prikler
2022-09-18 18:35       ` Liliana Marie Prikler
2022-09-19  6:04         ` Konrad Hinsen
2022-09-19  8:51           ` Konrad Hinsen
2022-10-02  0:15             ` Thompson, David
2022-10-02  0:23               ` Liliana Marie Prikler
2022-10-02  8:25               ` Konrad Hinsen
2022-10-12 19:42                 ` Liliana Marie Prikler [this message]
2022-10-13  9:31                   ` Max Brieiev
2022-10-13 18:23                     ` Liliana Marie Prikler
2022-10-14 16:07                   ` zimoun
2022-10-14 18:22                     ` Liliana Marie Prikler
2022-10-15 10:11                       ` zimoun
2022-10-15 14:40                         ` Liliana Marie Prikler
2022-10-15 15:40                           ` zimoun
2022-10-15 16:30                             ` Liliana Marie Prikler
2022-10-25 16:23                               ` Max Brieiev
2022-10-25 18:31                                 ` Liliana Marie Prikler
2022-10-26  7:46                                   ` zimoun
2022-10-11 10:04               ` zimoun
2022-10-13 10:06                 ` Max Brieiev
2023-10-12 14:50       ` bug#57878: Emacs native compilation on startup can crash the system Ludovic Courtès
2023-10-14 14:37         ` Konrad Hinsen
2022-12-09 14:30 ` bug#57878: Some further investigation Konrad Hinsen

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=6873fe86a05a548e7427d2de7df04a27a967713a.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=57878@debbugs.gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=konrad.hinsen@fastmail.net \
    /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).