From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com,
Ken Brown via Cygwin-announce <cygwin-announce@cygwin.com>
Subject: Re: [ANNOUNCEMENT] emacs 28.2-2 (64-bit only, TEST)
Date: Sat, 17 Sep 2022 15:35:26 -0400 [thread overview]
Message-ID: <4b662a72-0839-1273-473f-c168e2963ace@cs.umass.edu> (raw)
In-Reply-To: <announce.98b8e1f6-5752-3138-04ca-ed724f1dd8ff@cornell.edu>
On 9/17/2022 7:56 AM, Ken Brown via Cygwin-announce wrote:
> The following packages have been uploaded to the Cygwin distribution as test releases.
>
> * emacs-28.2-2
> * emacs-basic-28.2-2
> * emacs-w32-28.2-2
> * emacs-gtk-28.2-2
> * emacs-lucid-28.2-2
> * emacs-common-28.2-2
>
> This is the same as emacs-28.2-1, but it is built with the native compilation feature (explained
> below).
...
> The first few times you run Emacs, it might seem slow to start. This is
> because it is compiling the elisp libraries that are needed for your init
> file (usually .emacs). For the same reason, you might see occasional pauses
> the first time you use a command. But otherwise you should see a noticeable
> speed-up of Emacs.
Actually, I am not seeing that. The setup as provided does the native
compilation in deferred mode, which forks asynchronous native code
compilation, apparently while continuing to run byte code. When the native
code is ready, it is swapped in, replacing the interpreted byte code. So, if
your system has multiple cores (like mine) and is not overloaded, you may not
see slow down - only eventual speed up.
Thank you for this, Ken!
Eliot Moss
prev parent reply other threads:[~2022-09-17 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 11:56 Ken Brown via Cygwin-announce
2022-09-17 16:53 ` Jim Reisert AD1C
2022-09-17 19:35 ` Eliot Moss [this message]
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=4b662a72-0839-1273-473f-c168e2963ace@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin-announce@cygwin.com \
--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).