From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: perry@piermont.com, emacs-devel@gnu.org
Subject: Re: Speed of keyboard macro execution?
Date: Thu, 10 Dec 2015 22:13:57 +0100 [thread overview]
Message-ID: <87d1ueroq2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8337va9giv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Dec 2015 22:48:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: David Kastrup <dak@gnu.org>
>> Date: Thu, 10 Dec 2015 21:36:14 +0100
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>>
>> John Wiegley <jwiegley@gmail.com> writes:
>>
>> >>>>>> Perry E Metzger <perry@piermont.com> writes:
>> >
>> >> On Thu, 10 Dec 2015 22:00:05 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> >>> > From: David Kastrup <dak@gnu.org>
>> >>> > So I think it would make excellent sense to disable visual
>> >>> > positioning modes while recording and replaying keyboard macros.
>> >>>
>> >>> No, I think you are wrong. Think C-n and C-p again.
>> >
>> > Recording a macro has the value that it does what the user would have
>> > done, just automated. If you disable visual positioning, then in many
>> > cases it no longer does what I would have done manually.
>>
>> Visual positioning makes no sense without visual feedback. Can you show
>> a single example of a task to be done by a keyboard macro where visual
>> positioning would _help_ achieve that task rather than sabotage it?
>
> Even if I agree with you, it doesn't help to fix the _interactive_ use
> case of pressing C-p. With very long lines, that can take an
> eternity. _That_ is what we should strive to fix.
No argument here. My proposal changing the keyboard macro execution to
switch off visual positioning was not intended as a performance fix: it
might have that effect on some benchmarks, but that's purely incidental.
Stuff like fill-paragraph will still require display engine calculations
and I'm fine with that. Its purpose is not in any manner different
during macro recording/replay so it's definitely both useful and
consistent to consult the display engine.
With regard to visual movement, I don't see that consistency will ever
be useful in macro recording/replay. So I'd at least like to have an
option (effective during both macro recording and replay since a
difference between the two would be both inconsistent and useless) to
get inconsistent but useful behavior here.
--
David Kastrup
next prev parent reply other threads:[~2015-12-10 21:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 21:39 Speed of keyboard macro execution? Perry E. Metzger
2015-12-09 22:13 ` David Engster
2015-12-09 23:03 ` Perry E. Metzger
2015-12-10 16:43 ` Eli Zaretskii
2015-12-10 17:00 ` Perry E. Metzger
2015-12-10 17:14 ` John Wiegley
2015-12-10 17:27 ` David Engster
2015-12-10 17:33 ` Perry E. Metzger
2015-12-10 17:39 ` David Engster
2015-12-10 17:53 ` Eli Zaretskii
2015-12-10 18:10 ` Perry E. Metzger
2015-12-10 18:41 ` Eli Zaretskii
2015-12-10 18:44 ` David Kastrup
2015-12-10 18:57 ` Eli Zaretskii
2015-12-10 19:38 ` David Kastrup
2015-12-10 20:00 ` Eli Zaretskii
2015-12-10 20:09 ` David Kastrup
2015-12-10 20:43 ` Eli Zaretskii
2015-12-10 20:55 ` David Kastrup
2015-12-10 20:16 ` Perry E. Metzger
2015-12-10 20:18 ` John Wiegley
2015-12-10 20:36 ` David Kastrup
2015-12-10 20:43 ` John Wiegley
2015-12-10 21:01 ` David Kastrup
2015-12-10 21:26 ` John Wiegley
2015-12-10 23:35 ` David Kastrup
2015-12-11 1:14 ` John Wiegley
2015-12-11 6:27 ` David Kastrup
2015-12-12 22:56 ` John Wiegley
2015-12-12 23:46 ` David Kastrup
2015-12-13 0:16 ` John Wiegley
2015-12-13 0:32 ` David Kastrup
2015-12-12 23:20 ` Per Starbäck
2015-12-12 16:51 ` Perry E. Metzger
2015-12-12 17:42 ` David Kastrup
2015-12-12 23:01 ` Disabling visual lines for macros (was: Speed of keyboard macro execution?) John Wiegley
2015-12-12 23:33 ` Disabling visual lines for macros David Kastrup
2015-12-10 20:45 ` Speed of keyboard macro execution? Perry E. Metzger
2015-12-10 20:50 ` John Wiegley
2015-12-10 20:48 ` Eli Zaretskii
2015-12-10 20:50 ` John Wiegley
2015-12-10 21:13 ` David Kastrup [this message]
2015-12-10 17:37 ` Eli Zaretskii
2015-12-10 17:43 ` John Wiegley
2015-12-10 17:54 ` Eli Zaretskii
2015-12-10 18:15 ` Achim Gratz
2015-12-10 18:47 ` Eli Zaretskii
2015-12-12 2:14 ` Joseph Mingrone
2015-12-12 7:39 ` Eli Zaretskii
2015-12-12 17:28 ` Joseph Mingrone
2015-12-12 17:57 ` Eli Zaretskii
2015-12-12 18:12 ` Joseph Mingrone
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=87d1ueroq2.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).