From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: GNU Emacs 28.0.50 crash (emacs-w32)
Date: Thu, 7 Oct 2021 08:16:01 -0600 [thread overview]
Message-ID: <CAK-n8j5jYHBQnv3XbNL=wW-whGvkNewRRtJBQ+bRmssu3y2mGw@mail.gmail.com> (raw)
In-Reply-To: <fb045d31-3f89-2f13-7d47-dd4328decca0@cornell.edu>
> Could this be the following problem that I mentioned in the release announcement?
>
> > Compilation is done asynchronously, with a log in a buffer called
> > *Async-native-compile-log*. If you run emacs-w32 and exit while a
> > compilation is in progress, you might see a dialog box saying that
> > emacs has aborted and asking if you want to attach a debugger. Just
> > say No. If this annoys you, check the compilation buffer before
> > exiting, and wait for the "Compilation finished" message.
>
> I'll add one more thing that I didn't know when I wrote that: You can customize
> the variable native-comp-async-query-on-exit if you want to be warned that there
> are compilations in process when you exit.
Sure, that could be the problem. I'll try the workaround.
I do notice that there are separate compilation directories for emacs
and emacs-w32. Is this necessary?
[JJR:/cygdrive/e/] $ new ~/.emacs.d/eln-cache/
total 28
drwxrwx---+ 1 jjrei jjrei 0 Oct 3 15:44 28.0.50-eb740d6f
drwxrwx---+ 1 jjrei jjrei 0 Oct 6 08:17 28.0.50-891fd08c
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us
next prev parent reply other threads:[~2021-10-07 14:16 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 [this message]
2021-10-07 14:53 ` Ken Brown
2021-10-07 16:04 ` Jim Reisert AD1C
2021-10-07 20:21 ` Jim Reisert AD1C
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-n8j5jYHBQnv3XbNL=wW-whGvkNewRRtJBQ+bRmssu3y2mGw@mail.gmail.com' \
--to=jjreisert@alum.mit.edu \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).