From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs 28.0.60-1.f7e6c199bf (TEST)
Date: Sun, 24 Oct 2021 16:13:46 -0400 [thread overview]
Message-ID: <f09dece7-0765-22d2-26be-4732600d1ab5@cornell.edu> (raw)
In-Reply-To: <CAK-n8j7tiD9+7pSGHCc7XNx5GK66bS++Xv=xLoZ5p5fi7F9RBA@mail.gmail.com>
On 10/18/2021 3:15 PM, Jim Reisert AD1C wrote:
> Here is a macro I use quite frequently, with a line like this:
>
> # New Exception Call: PD0TEST/J
>
> The macro consists of:
>
> - CTRL-A
> - set mark
> - CTRL-F until you get to the start of the field after Call:
> - CTRL-W to delete the selected text
> - CTRL-N to go to the start of the next line
>
> After the macro is defined, there is a pause the next (first) time it's
> used (C-x C-e). It's speedy after that.
You mean 'C-x e', not 'C-x C-e', right?
I just inserted several lines like
# New Exception Call: PD0TEST/J
into the *scratch* buffer and defined your keyboard macro. I didn't notice any
delay the first time I ran it. Might there be some other conditions necessary
to reproduce the problem? Is the mode of the buffer relevant? Can you
reproduce the problem starting from 'emacs -Q'?
Ken
next prev parent reply other threads:[~2021-10-24 20:13 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
2021-10-18 19:15 ` Jim Reisert AD1C
2021-10-24 20:13 ` Ken Brown [this message]
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=f09dece7-0765-22d2-26be-4732600d1ab5@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).