unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Strange behavior of C-u in the presence of sit-for in p-c-h
Date: Tue, 17 Oct 2006 22:19:06 -0400	[thread overview]
Message-ID: <878xjext5x.fsf@furball.mit.edu> (raw)
In-Reply-To: <jwv4pu2o0nz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue\, 17 Oct 2006 21\:57\:17 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Maybe the problem is that `this-command-keys' has several potential uses and
> they are incompatible: in one case one wants this-command-keys to list the
> keys the user has typed (independently from whether or not some of those
> keys were later read&unread&reread&reunread&rereread), whereas in the other
> one wants the exact key-sequence which triggered this command, so we can
> push it back on unread-command-events to force re-interpretation of
> those keys.

Given that the code has been around for 8 years, changing it at this
point in the release process might be a disaster.  It's not even clear
to me what TRT is in this case.  I suggest leaving the current
behavior as it is for Emacs 22; any user-level Lisp code that bumps
into this can quite easily work around it by checking if this-command
is eq to universal-argument.

Then maybe we can revisit this issue after the release.  WDYT?

  reply	other threads:[~2006-10-18  2:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14 16:44 Strange behavior of C-u in the presence of sit-for in p-c-h Stefan Monnier
2006-10-16 13:50 ` Richard Stallman
2006-10-16 16:04   ` Stefan Monnier
2006-10-17  6:54     ` Richard Stallman
2006-10-17 14:50       ` Chong Yidong
2006-10-17 21:11         ` Chong Yidong
2006-10-17 22:12           ` Stefan Monnier
2006-10-17 22:18             ` Chong Yidong
2006-10-18  1:57           ` Stefan Monnier
2006-10-18  2:19             ` Chong Yidong [this message]
2006-10-18  5:57               ` Stefan Monnier
2006-10-18 14:28                 ` Chong Yidong
2006-10-18 15:23                   ` Stefan Monnier
2006-10-19  6:41                     ` Richard Stallman
2006-10-19  6:41                   ` Richard Stallman
2006-10-19 14:31                     ` Chong Yidong
2006-10-19 14:51                   ` Johan Bockgård
2006-10-18 17:54             ` Richard Stallman
2006-10-18 23:57               ` Chong Yidong
2006-10-19  9:01                 ` Kim F. Storm
2006-10-19 21:09         ` Kim F. Storm
2006-10-19 21:25           ` Chong Yidong
2006-10-19 21:09         ` Kim F. Storm
2006-10-21  2:03           ` Richard Stallman
2006-10-22 22:54             ` Kim F. Storm

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=878xjext5x.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).