From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Alex Schroeder Newsgroups: gmane.emacs.devel Subject: Re: signal handling bogosities Date: Fri, 20 Dec 2002 19:35:14 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87bs3gczdp.fsf@emacswiki.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1040409385 32176 80.91.224.249 (20 Dec 2002 18:36:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 20 Dec 2002 18:36:25 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18PS0W-0008Mq-00 for ; Fri, 20 Dec 2002 19:36:24 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18PS2E-0002CE-00 for ; Fri, 20 Dec 2002 19:38:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18PS08-0000G8-0A for emacs-devel@quimby.gnus.org; Fri, 20 Dec 2002 13:36:00 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18PRzb-0008Ii-00 for emacs-devel@gnu.org; Fri, 20 Dec 2002 13:35:27 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18PRzT-0007wC-00 for emacs-devel@gnu.org; Fri, 20 Dec 2002 13:35:23 -0500 Original-Received: from isp247n.hispeed.ch ([62.2.95.247] helo=smtp.hispeed.ch) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18PRzQ-0007nh-00 for emacs-devel@gnu.org; Fri, 20 Dec 2002 13:35:16 -0500 Original-Received: from confusibombus (dclient217-162-33-124.hispeed.ch [217.162.33.124])gBKIZEVg031168 for ; Fri, 20 Dec 2002 19:35:15 +0100 Original-Received: from alex by confusibombus with local (Exim 3.35 #1 (Debian)) id 18PRzO-00005b-00 for ; Fri, 20 Dec 2002 19:35:14 +0100 Original-To: emacs-devel@gnu.org X-Face: ^BC$`[IcggstLPyen&dqF+b2'zyK#r.mU*'Nms}@&4zw%SJ#5!/7SMVjBS7'lb; QK)|IPU5U'o1'522W4TyzB3Ab*IBo^iw]l4|kUbdZuUDO6=Um-.4IzhNiV'B"@K#jy_(wW|Zbk[34flKY^|PrQ?$u2\fKg^]AY>wOX#H32i In-Reply-To: (Richard Stallman's message of "Fri, 20 Dec 2002 12:12:24 -0500") Original-Lines: 17 User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2.92 (i686-pc-linux-gnu) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:10310 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:10310 Richard Stallman writes: > If we handle mouse highlighting by generating input events to do the > work at main program level, then the highlighting won't change when > you move the mouse while Emacs is running a Lisp program. Is that > acceptable? >>From a user perspective, I think that is acceptable. Sure, currently most programs use a second thread for their GUI, so eventhough they are busy, you can open menus -- but when it gets to doing something, they are just as bound by the event queue as Emacs is -- you can open the menu, look at it, click on it, but things only happen when the previous job is done. Since users cannot do anything anyway when Emacs is busy, I think it is not a big plus to have highlighting working. Loosing that, therefore, is not a problem. Alex.