From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Re: GNU Emacs 28.0.50 crash (emacs-w32)
Date: Thu, 7 Oct 2021 14:21:19 -0600 [thread overview]
Message-ID: <CAK-n8j7N3rARvncD-HhepK35F6jXk7m3LXSxq4POSiWae8MXrw@mail.gmail.com> (raw)
In-Reply-To: <9d469b42-c28d-6f91-4258-e48e834ba2a5@cornell.edu>
> I'm about to announce a new test release that tries to work around the problem
> in a different way. I'd be interested in hearing how that works too.
I updated Emacs and turned off "native-comp-async-query-on-exit".
This time, there was no error report from emacs-w32, it just silently
exited while the compilation was ongoing. I don't know if that was
the desired outcome.
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us
next prev parent reply other threads:[~2021-10-07 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 14:22 Jim Reisert AD1C
2021-10-06 14:25 ` Jim Reisert AD1C
2021-10-06 15:38 ` Ken Brown
2021-10-06 15:47 ` Ken Brown
2021-10-07 14:16 ` Jim Reisert AD1C
2021-10-07 14:53 ` Ken Brown
2021-10-07 16:04 ` Jim Reisert AD1C
2021-10-07 20:21 ` Jim Reisert AD1C [this message]
2021-10-08 16:18 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK-n8j7N3rARvncD-HhepK35F6jXk7m3LXSxq4POSiWae8MXrw@mail.gmail.com \
--to=jjreisert@alum.mit.edu \
--cc=cygwin@cygwin.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.
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).