From: David Kastrup <dak@gnu.org>
Subject: Re: Keyboard macros updating screen
Date: Thu, 29 Jun 2006 16:47:12 +0200 [thread overview]
Message-ID: <85u0643tov.fsf@lola.goethe.zz> (raw)
In-Reply-To: 1151589543.134249.327230@i40g2000cwc.googlegroups.com
"Arndt Jonasson" <arndt.jonasson@gmail.com> writes:
> Is there any way to tell a keyboard macro to just
> do whatever it is supposed to do, and not update
> the screen for each change that it makes to the
> buffer? Comparing with previous versions of Emacs
> (I upgraded recently), the behaviour I'm seeing is
> so slow that keyboard macros seem virtually useless.
>
> My Emacs version is 21.4.
Using a developer snapshot should make life quite more pleasant. What
is your operating system?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-06-29 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 13:59 Keyboard macros updating screen Arndt Jonasson
2006-06-29 14:47 ` David Kastrup [this message]
2006-06-29 15:13 ` Arndt Jonasson
2006-06-29 15:23 ` Brendan Halpin
2006-06-29 16:15 ` Romain Francoise
2006-06-29 17:24 ` Brendan Halpin
2006-06-29 17:38 ` Romain Francoise
2006-06-29 21:01 ` Leon
2006-06-29 18:22 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85u0643tov.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/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).