[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dabbrev-expand should escape kbd macros, shouldn't it?
From: |
Andreas Schwab |
Subject: |
Re: dabbrev-expand should escape kbd macros, shouldn't it? |
Date: |
Wed, 17 Jul 2019 17:52:26 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2.90 (gnu/linux) |
On Jul 17 2019, "Daniel Colascione" <address@hidden> wrote:
> Right now, if you record a kbd macro and hit M-/, the act of hitting M-/
> is recorded like any other command in the kbd macro. On replay, we'll run
> dabbrev-expand. The problem is that dabbrev-expand produces radically
> different results depending on buffer context, making macro replay
> unpredictable. Should the *result* of dabbrev-expand just get put into the
> kbd macro instead?
How is that different from any other key that is part of the macro? The
point of a kbd macro is to record keys, not their effect (or even their
binding).
Andreas.
--
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."