Re: Speed of keyboard macro execution?

[Eli Zaretskii]

> From: David Kastrup <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Thu, 10 Dec 2015 20:38:58 +0100
> 
> >> Tying the operation of keyboard macros to the current display/font
> >> selection is just meaningless.  Its purpose is for _aiming_ positioning
> >> by keyboard, and that's just not useful at keyboard replay.
> >
> > I think it depends on the keyboard macro.  The ones I saw in that demo
> > did move point, moreover they moved it to the end of a very long line,
> > so both the actual redisplay and its simulation were at work,
> > including auto-hscroll.
> 
> So how did line-move-visual accomplish anything useful here?

One example is vertical-motion, and many commands that call it.  E.g.,
if the macro invokes C-n.

> > In any case, keyboard macros are not relevant to the discussion
> > (contrary to the subject line).  The issue is slow redisplay with long
> > lines.
> 
> Which occured during keyboard macro execution due to line-move-visual
> being active.

No, not necessarily.  Rather, the original issue with keyboard macros
is just one of the scenarios that brings the broader problem to light,
if the macro invokes one of the affected commands.

> 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.