RE: dabbrev-expand should escape kbd macros, shouldn't it?

[Drew Adams <drew.adams@oracle.com>]

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

+1

A keyboard macro is essentially a command.

You generally want to be able to replay a keyboard macro
(keystrokes) in various contexts.  You generally do not
want to capture the original context as part of the macro.