From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs 28.0.60-1.f7e6c199bf (TEST)
Date: Fri, 15 Oct 2021 11:22:52 -0400 [thread overview]
Message-ID: <30f36c61-a7b6-c15a-f083-02b69ee0bbfa@cornell.edu> (raw)
In-Reply-To: <CAK-n8j7n5P6T2qFkB_OdirLAK3jBqOSrNNyW+nf_1Bv57e3iDA@mail.gmail.com>
On 10/14/2021 10:38 AM, Jim Reisert AD1C wrote:
>>> I have noticed one slight performance issue, which may not be related
>>> to Cygwin at all.
>>>
>>> After creating a keyboard macro, the first time the macro is
>>> used/called (^x^e), it does not start right away. Subsequent uses are
>>> as fast as expected. Could some sort of run-time compilation going on
>>> in the background before the keyboard macro executes the first time?
>>>
>>> As I said, this may not be related to Cygwin at all.
>>
>> This is mentioned in the announcement for emacs 28.0.60-1.f7e6c199bf (TEST)
>>
>> 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.
>
> I'm not talking about startup or commands. I'm talking about keyboard
> macros which are not mentioned in the paragraph above. I've already
> experienced those symptoms described.
I've defined a few keyboard macros and haven't noticed any delay, but they were
very short. Do you have a reproducible recipe?
Ken
next prev parent reply other threads:[~2021-10-15 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 15:33 [ANNOUNCEMENT] " Ken Brown via Cygwin-announce
2021-10-13 20:22 ` Jim Reisert AD1C
2021-10-14 0:24 ` David Billinghurst
2021-10-14 14:38 ` Jim Reisert AD1C
2021-10-15 15:22 ` Ken Brown [this message]
2021-10-18 19:15 ` Jim Reisert AD1C
2021-10-24 20:13 ` Ken Brown
2021-10-25 15:04 ` Jim Reisert AD1C
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=30f36c61-a7b6-c15a-f083-02b69ee0bbfa@cornell.edu \
--to=kbrown@cornell.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).