From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: two related edebug problems Date: Sat, 12 Aug 2006 02:19:36 +0200 Message-ID: References: <2cd46e7f0608071130o7d72123ct82841031bf757f5d@mail.gmail.com> <2cd46e7f0608081226o63f2a0d5q9e79575021d0a181@mail.gmail.com> <873bc4k1yl.fsf@furball.mit.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1155342108 5891 80.91.229.2 (12 Aug 2006 00:21:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 12 Aug 2006 00:21:48 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org, Ken Manheimer , rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 12 02:21:45 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 1GBhFx-0004Wf-AC for ged-emacs-devel@m.gmane.org; Sat, 12 Aug 2006 02:21:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GBhFw-0005Bj-Hn for ged-emacs-devel@m.gmane.org; Fri, 11 Aug 2006 20:21:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GBhFj-000596-FN for emacs-devel@gnu.org; Fri, 11 Aug 2006 20:21:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GBhFe-00053y-MN for emacs-devel@gnu.org; Fri, 11 Aug 2006 20:21:22 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GBhFe-00053r-G7 for emacs-devel@gnu.org; Fri, 11 Aug 2006 20:21:18 -0400 Original-Received: from [195.41.46.235] (helo=pfepa.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GBhKp-0004zH-PY; Fri, 11 Aug 2006 20:26:39 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepa.post.tele.dk (Postfix) with SMTP id F1731FAC01C; Sat, 12 Aug 2006 02:20:57 +0200 (CEST) Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Fri, 11 Aug 2006 18:34:29 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:58306 Archived-At: Stefan Monnier writes: > This is a workaround rather than a fix. A real fix would be to change > sit-for so it doesn't use unread-command-events but an internal variable > instead with which other code can't mess. We currently have the following "unread event" variables (in order of usage): unread-post-input-method-events unread-command-char (obsolete) unread-command-events unread-input-method-events unread_switch_frame (C internal) At which step should unread-sit-for-event be placed? I.e. if some timer function actually places something on unread-command-events, should that be interpreted before or after unread-sit-for-event ?? BTW, unread-post-input-method-events and unread-input-method-events have the _same_ doc string: List of events to be processed as input by input methods. These events are processed after `unread-command-events', but before actual keyboard input. */); According to the sequence in the code, "after" should be "before" for unread-post-input-method-events. But the name of these vars puzzles me... since the -post- thing is actually run _before_ the other vars...?? Maybe the doc strings need some clarification... -- Kim F. Storm http://www.cua.dk