From: Richard Stallman <rms@gnu.org>
Cc: belanger@truman.edu, emacs-devel@gnu.org
Subject: Re: Behavior of `this-command-keys'
Date: Wed, 13 Sep 2006 11:10:09 -0400 [thread overview]
Message-ID: <E1GNWNN-0005zp-S4@fencepost.gnu.org> (raw)
In-Reply-To: <87hczdyr5w.fsf@vh213602.truman.edu> (message from Jay Belanger on Tue, 12 Sep 2006 11:40:27 -0500)
> It seems that the documentation of this-command-keys is wrong. Its
> value seems to include any keys that were read by read-event.
I take it that's the desired value, then.
Yes, I think it was intentional. I believe my patch restores
the behavior as of before the sit-for change.
prev parent reply other threads:[~2006-09-13 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 17:54 Behavior of `this-command-keys' Jay Belanger
2006-09-11 22:13 ` Kim F. Storm
2006-09-12 16:42 ` Jay Belanger
2006-09-12 2:01 ` Richard Stallman
2006-09-12 16:40 ` Jay Belanger
2006-09-13 15:10 ` Richard Stallman [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=E1GNWNN-0005zp-S4@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=belanger@truman.edu \
--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).