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: 13 Dec 2003 18:35:22 +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 1AVDil-0006Uu-00 for ; Sat, 13 Dec 2003 18:38:27 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AVDil-0000y6-00 for ; Sat, 13 Dec 2003 18:38:27 +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 1AVEe9-0007jz-8s for emacs-devel@quimby.gnus.org; Sat, 13 Dec 2003 13:37:45 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AVEe3-0007jn-W5 for emacs-devel@gnu.org; Sat, 13 Dec 2003 13:37:39 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AVEdV-0007JI-Mh for emacs-devel@gnu.org; Sat, 13 Dec 2003 13:37:36 -0500 Original-Received: from [62.226.12.137] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AVEdU-0007DU-M4; Sat, 13 Dec 2003 13:37:05 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hBDHZUGH015264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Dec 2003 18:35:31 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hBDHZMOa015260; Sat, 13 Dec 2003 18:35:22 +0100 Original-To: Eli Zaretskii In-Reply-To: <3791-Sat13Dec2003181125+0200-eliz@elta.co.il> Original-Lines: 29 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:18673 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18673 "Eli Zaretskii" writes: > > From: Richard Stallman > > Date: Fri, 12 Dec 2003 18:55:58 -0500 > > > > Redisplay could set a flag to prevent thread-switching. > > I think making redisplay a separate thread would be one of the more > useful improvements in Emacs. The situation where the user clicks > File->Open from the menu bar and then (under a toolkit), while the > file-selection box is active, the Emacs display never changes, looks > like a bug. (Try moving the file-selection box to a different > position and observe the blank portions of the Emacs window.) 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. More seriously, I had quite a few times paste operations go quite to the wrong place when something affecting the buffer display was running in background, even though at the time of the click the display was still something quite different. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum