From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: What's the problem? Date: 14 Dec 2003 12:55:48 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu> <5bad69zd43.fsf@lister.roxen.com> <4noeuon378.fsf@lockgroove.bwh.harvard.edu> <4ny8tsgxy6.fsf@lockgroove.bwh.harvard.edu> <4nhe0ggv0u.fsf@lockgroove.bwh.harvard.edu> <4nk75bwjaf.fsf@lockgroove.bwh.harvard.edu> <4nsmjv8d32.fsf@collins.bwh.harvard.edu> <87iskpbloe.fsf@mail.jurta.org> Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AVUsb-00014s-00 for ; Sun, 14 Dec 2003 12:57:45 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AVUsb-0003hh-00 for ; Sun, 14 Dec 2003 12:57:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AVVpN-0007jm-PR for emacs-devel@quimby.gnus.org; Sun, 14 Dec 2003 07:58:29 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AVVp3-0007bQ-No for emacs-devel@gnu.org; Sun, 14 Dec 2003 07:58:09 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AVVoV-00073f-00 for emacs-devel@gnu.org; Sun, 14 Dec 2003 07:58:06 -0500 Original-Received: from [217.80.157.143] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AVVoU-00071x-Ay for emacs-devel@gnu.org; Sun, 14 Dec 2003 07:57:34 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hBEBtu82026113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Dec 2003 12:55:57 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hBEBtnET026109; Sun, 14 Dec 2003 12:55:49 +0100 Original-To: Eli Zaretskii In-Reply-To: Original-Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18686 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18686 Eli Zaretskii writes: > > From: David Kastrup > > Date: 13 Dec 2003 18:35:22 +0100 > > > > It would also be an idea, if one has a redisplay thread, to let it > > associate mouse clicks with objects under it at the time of the click. > > People rarely expect, when they click in the text area while Emacs is > > busy, that half an hour later a menu pops up with a button "Really > > self-destruct?" which happens to be right on the location where the > > click had been half an hour ago, that this menu/text position etc will > > be satisfied with the click from olden times. > > I think, with a separate thread, such cases will be less probable, > actually, since the redisplay will have more chance to catch up with > the rest of Emacs than it is now. It can't catch up with a state of Emacs that Emacs has not yet reached at the time of the click. At the time posn-point is called, the state of Emacs might be quite different from the state at the time of the click. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum