From: Eli Zaretskii <eliz@gnu.org>
To: Hin-Tak Leung <htl10@users.sourceforge.net>,
Andrea Corallo <akrl@sdf.org>
Cc: 60208@debbugs.gnu.org
Subject: bug#60208: 28.1; Resource exhaustion with emacs 28's native compilation; need "-Q" for trampoline
Date: Tue, 20 Dec 2022 16:16:23 +0200 [thread overview]
Message-ID: <83a63icg94.fsf@gnu.org> (raw)
In-Reply-To: <1097810616.3252016.1671528631492@mail.yahoo.com> (message from Hin-Tak Leung on Tue, 20 Dec 2022 09:30:31 +0000 (UTC))
> Date: Tue, 20 Dec 2022 09:30:31 +0000 (UTC)
> From: Hin-Tak Leung <htl10@users.sourceforge.net>
> Cc: 60208@debbugs.gnu.org
>
> On Tuesday, 20 December 2022 at 11:32:21 GMT+8, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > I'm not sure this conclusion is correct, because --batch implies -q.
> > There's a difference between -q and -Q, so are you saying that
> > emacs-ess is loaded from a site-init file in your case?
>
> Yes, that's right. Fedora has a "/usr/share/emacs/site-lisp/site-start.d/ess-init.el" , which contains the single
> line, "(require 'ess-site)". Indeed as you said.
Thanks.
Andrea, do you see any problems with adding -Q to the async
compilation command line, to avoid processing site-init files? Did we
have any reasons not to do that from the beginning, or was it just an
omission?
next prev parent reply other threads:[~2022-12-20 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <974722961.3073608.1671487166201.ref@mail.yahoo.com>
2022-12-19 21:59 ` bug#60208: 28.1; Resource exhaustion with emacs 28's native compilation; need "-Q" for trampoline Hin-Tak Leung
2022-12-20 3:32 ` Eli Zaretskii
2022-12-20 9:30 ` Hin-Tak Leung
2022-12-20 14:16 ` Eli Zaretskii [this message]
2022-12-21 9:25 ` Andrea Corallo
2022-12-21 12:46 ` Eli Zaretskii
2022-12-21 22:30 ` Andrea Corallo
2022-12-22 0:33 ` Hin-Tak Leung
2022-12-22 7:21 ` Eli Zaretskii
2022-12-22 13:46 ` Hin-Tak Leung
2022-12-22 15:22 ` Eli Zaretskii
2022-12-22 16:32 ` Hin-Tak Leung
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a63icg94.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60208@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=htl10@users.sourceforge.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/emacs.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).