From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: repeatable vs. non-repeatable commands
Date: Mon, 26 Jun 2017 17:31:18 +0200 [thread overview]
Message-ID: <87r2y6u5o9.fsf@drachen> (raw)
In-Reply-To: <jwvo9tdbk70.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Sat, 24 Jun 2017 09:23:29 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I just sent a workaround for bug#27470 that you might be able to use
> (i.e. call this-command-keys(-vector) at the very beginning).
>
> E.g. [...]
Thank you, I'll probably go with something like that.
Michael.
prev parent reply other threads:[~2017-06-26 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 6:17 repeatable vs. non-repeatable commands Michael Heerdegen
2017-06-24 10:01 ` Emanuel Berg
2017-06-25 4:56 ` Michael Heerdegen
2017-06-25 15:53 ` Emanuel Berg
2017-06-26 13:49 ` Michael Heerdegen
2017-06-24 10:22 ` Emanuel Berg
2017-06-25 4:59 ` Michael Heerdegen
2017-06-25 16:22 ` Emanuel Berg
2017-06-24 13:23 ` Stefan Monnier
2017-06-26 15:31 ` Michael Heerdegen [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=87r2y6u5o9.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).