From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel 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 Message-ID: <878xjext5x.fsf@furball.mit.edu> References: <87y7rfdmjg.fsf@furball.mit.edu> <87zmbuabq9.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1161137992 20726 80.91.229.2 (18 Oct 2006 02:19:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 18 Oct 2006 02:19:52 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 18 04:19:49 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Ga124-0001Im-Tb for ged-emacs-devel@m.gmane.org; Wed, 18 Oct 2006 04:19:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ga124-0005yx-0T for ged-emacs-devel@m.gmane.org; Tue, 17 Oct 2006 22:19:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ga11q-0005vt-SZ for emacs-devel@gnu.org; Tue, 17 Oct 2006 22:19:34 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ga11q-0005vd-GZ for emacs-devel@gnu.org; Tue, 17 Oct 2006 22:19:34 -0400 Original-Received: from [18.72.1.2] (helo=south-station-annex.mit.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Ga11q-0004SE-Cb; Tue, 17 Oct 2006 22:19:34 -0400 Original-Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by south-station-annex.mit.edu (8.13.6/8.9.2) with ESMTP id k9I2JUfG013050; Tue, 17 Oct 2006 22:19:30 -0400 (EDT) Original-Received: from outgoing-legacy.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104]) by central-city-carrier-station.mit.edu (8.13.6/8.9.2) with ESMTP id k9I2JQqs022907; Tue, 17 Oct 2006 22:19:26 -0400 (EDT) Original-Received: from furball.mit.edu (SYDNEYPACIFIC-FOUR-O-THREE.MIT.EDU [18.95.6.148]) ) by outgoing-legacy.mit.edu (8.13.6/8.12.4) with ESMTP id k9I2J7cN002090; Tue, 17 Oct 2006 22:19:09 -0400 (EDT) Original-Received: from cyd by furball.mit.edu with local (Exim 3.36 #1 (Debian)) id 1Ga11O-0000jH-00; Tue, 17 Oct 2006 22:19:06 -0400 Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Tue\, 17 Oct 2006 21\:57\:17 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-Spam-Score: 1.217 X-Scanned-By: MIMEDefang 2.42 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:60854 Archived-At: Stefan Monnier 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?