From: Andrea Corallo <akrl@sdf.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org, Andrea Corallo <andrea.corallo@arm.com>
Subject: Re: master 5ad5b797f7: Set `comp-no-spawn' earlier using -no-comp-spawn
Date: Mon, 31 Oct 2022 13:11:01 +0000 [thread overview]
Message-ID: <xjfh6zkf89m.fsf@ma.sdf.org> (raw)
In-Reply-To: <87v8o18mw6.fsf@melete.silentflame.com> (Sean Whitton's message of "Sun, 30 Oct 2022 06:24:41 -0700")
Sean Whitton <spwhitton@spwhitton.name> writes:
> Hello,
>
> On Wed 26 Oct 2022 at 02:37AM -04, Andrea Corallo wrote:
>
>> branch: master
>> commit 5ad5b797f78dacb9c901d3c63bee05b1762fa94f
>> Author: Andrea Corallo <andrea.corallo@arm.com>
>> Commit: Andrea Corallo <andrea.corallo@arm.com>
>>
>> Set `comp-no-spawn' earlier using -no-comp-spawn
>>
>> * src/emacs.c (standard_args): Add '-no-comp-spawn' cmd line option.
>> * lisp/startup.el (command-line): Parse '-no-comp-spawn' cmd line
>> option.
>> * lisp/emacs-lisp/comp.el (comp-run-async-workers, comp-final):
>> Use '-no-comp-spawn'.
>> ---
>> lisp/emacs-lisp/comp.el | 10 +++++-----
>> lisp/startup.el | 5 ++++-
>> src/emacs.c | 1 +
>> 3 files changed, 10 insertions(+), 6 deletions(-)
>
> I backported this to Emacs 28 for,
I guess it means Debian is maintaining it's own emacs28 branch?
> Debian and it has solved the problem for at least one of the bug
> reporters -- thank you.
Happy to help :)
Andrea
next prev parent reply other threads:[~2022-10-31 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166676623157.8660.10119995695510020779@vcs2.savannah.gnu.org>
[not found] ` <20221026063711.ED11AC00AB5@vcs2.savannah.gnu.org>
2022-10-30 13:24 ` master 5ad5b797f7: Set `comp-no-spawn' earlier using -no-comp-spawn Sean Whitton
2022-10-31 13:11 ` Andrea Corallo [this message]
2022-10-31 20:40 ` Sean Whitton
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=xjfh6zkf89m.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=andrea.corallo@arm.com \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).