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>, 57878@debbugs.gnu.org
Subject: bug#57878: Minimal reproducible setup
Date: Sun, 18 Sep 2022 01:19:57 +0200	[thread overview]
Message-ID: <e00fb97ec9fa651b42c7bbbf29760e0d93e6e3e6.camel@gmail.com> (raw)
In-Reply-To: <m1o7vexawf.fsf@fastmail.net>

Am Samstag, dem 17.09.2022 um 17:45 +0200 schrieb Konrad Hinsen:
> Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> 
> > Here is a minimal containerized example that
> > creates a process avalanche:
> > 
> >     guix shell -C emacs emacs-ido-completing-read+ \
> >        -- emacs --batch --eval="(print load-path)"
> 
> I went through all my emacs packages. The only one that starts
> the process avalanche is emacs-ido-completing-read+.
I think you can prevent native-compilation entirely by setting no-
native-compile to t in your early-init.el (I'm playing with the idea of
doing this anyway, because I'm annoyed by the clutter that falls
through the cracks).  That being said, this looks like a real breakage
in the emacs-ido-completing-read package, does it not?  Should we add
"no-native-compile" to some local variables?

WDYT?




  reply	other threads:[~2022-09-17 23:21 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 [this message]
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
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=e00fb97ec9fa651b42c7bbbf29760e0d93e6e3e6.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=57878@debbugs.gnu.org \
    --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).