> 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 wh
> >> 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.
>
The following packages have been uploaded to the Cygwin distribution
as test releases:
* emacs-28.0.60-1.f7e6c199bf
* emacs-common-28.0.60-1.f7e6c199bf
* emacs-X11-28.0.60-1.f7e6c199bf
* emacs-w32-28.0.60-1.f7e6c199bf
* emacs-lucid-28.0.60-1.f7e6c199bf
Emacs is a powerful, customizable, self-doc
On 10/7/2021 10:16 AM, Jim Reisert AD1C wrote:
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
> 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 tha
5 matches
Mail list logo