From: Andreas Schwab <schwab@suse.de>
To: "Daniel Colascione" <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: dabbrev-expand should escape kbd macros, shouldn't it?
Date: Wed, 17 Jul 2019 17:52:26 +0200 [thread overview]
Message-ID: <mvmlfww3bgl.fsf@suse.de> (raw)
In-Reply-To: <4ea4470ad1919b2f1915d6ec77f7d2b8.squirrel@dancol.org> (Daniel Colascione's message of "Wed, 17 Jul 2019 08:13:05 -0700")
On Jul 17 2019, "Daniel Colascione" <dancol@dancol.org> 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, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-07-17 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 15:13 dabbrev-expand should escape kbd macros, shouldn't it? Daniel Colascione
2019-07-17 15:52 ` Andreas Schwab [this message]
2019-07-17 17:39 ` Drew Adams
2019-07-17 18:30 ` Daniel Colascione
2019-07-18 7:32 ` Andreas Schwab
2019-07-18 22:22 ` Juri Linkov
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=mvmlfww3bgl.fsf@suse.de \
--to=schwab@suse.de \
--cc=dancol@dancol.org \
--cc=emacs-devel@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.
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).