From: Juri Linkov <juri@linkov.net>
To: "Daniel Colascione" <dancol@dancol.org>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: dabbrev-expand should escape kbd macros, shouldn't it?
Date: Fri, 19 Jul 2019 01:22:04 +0300 [thread overview]
Message-ID: <87a7dbnfub.fsf@mail.linkov.net> (raw)
In-Reply-To: <e6817d39ed9be00e678b38b9531cf830.squirrel@dancol.org> (Daniel Colascione's message of "Wed, 17 Jul 2019 11:30:54 -0700")
> Most of the time, recorded keystrokes in macros aren't that sensitive
> to _temporal_ and _interbuffer_ context, and dabbrev is, so I think we
> should make an exception for dabbrev.
Recently I had the same thoughts when a kbd macro recorded the paste
keystroke and not the text it pasted (as a sequence of self-inserting
keys). I know that it records just plain keystrokes, but in that context
the result was unexpected. However, I don't think that pasting should be
an exception. Maybe keyboard macros should provide a special macro-escape
feature (like there is a macro-query feature available via ‘C-x q’) to ask
whether to record the keystroke literally or to record the effect of
the command.
This ambiguity demonstrates why it's impossible to implement a package
that would convert keyboard macros to programs - because there are too
many logical levels of how the result of every keystroke can be interpreted
depending on expectancy even of the same user in different contexts.
prev parent reply other threads:[~2019-07-18 22:22 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
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 [this message]
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=87a7dbnfub.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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).