From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.devel Subject: Re: Bold by moving pixels problem Date: 21 Jan 2004 00:39:00 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200306041435.h54EZncl025672@rum.cs.yale.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: sea.gmane.org 1074664080 10486 80.91.224.253 (21 Jan 2004 05:48:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2004 05:48:00 +0000 (UTC) Cc: bob@rattlesnake.com, miles@gnu.org, emacs-devel@gnu.org, Stefan Monnier Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Jan 21 06:47:53 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AjBDV-0006bx-00 for ; Wed, 21 Jan 2004 06:47:53 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AjBDQ-0005Tn-00 for ; Wed, 21 Jan 2004 06:47:48 +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 1AjB7o-0007wc-09 for emacs-devel@quimby.gnus.org; Wed, 21 Jan 2004 00:42:00 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AjB6Y-0006Vk-H6 for emacs-devel@gnu.org; Wed, 21 Jan 2004 00:40:42 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AjB5F-0004PS-A1 for emacs-devel@gnu.org; Wed, 21 Jan 2004 00:39:53 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AjB55-00045l-5Q; Wed, 21 Jan 2004 00:39:11 -0500 Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id D17B220F98; Wed, 21 Jan 2004 00:39:00 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 7C6888C6F3; Wed, 21 Jan 2004 00:39:00 -0500 (EST) X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: gnu/emacs Original-To: Richard Stallman Original-Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=0, requis 5) 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:19384 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19384 > That's not quite accurate. The updating is about as immediate with > my synchronous signal handler as it is with the current async > signal handler, because it can take place any time QUIT is used, > which means "also in the middle of elisp code". > > Please forgive my confusion. > > I've been running with synchronous signal handlers since I mentioned > it on this list and I'm pretty happy with it. > > I think it would be good for more people to try it. I have installed patches to that effect. By default, nothing's changed. But if you define SYNC_INPUT, then signal handlers will only set a variable and the actual processing will be done from UNBLOCK_INPUT or from QUIT, whichever occurs sooner. Please try it out. Normally, the only problem you might encounter with the patch is that Emacs gets unresponsive. If that happens, please try to figure out how to reproduce it, and also try to get a (bunch of) C backtrace of when the unresponsiveness happens. I've been using a very similar patch for a while now with no problems. If SYNC_INPUT has no ill effect, it would be good to make it the default unconditionally. This would allow us to get rid of the ugly BLOCK_INPUT wrappers in alloc.c, for one thing. It would also make Emacs more stable by removing a whole class of hard to reproduce bugs (we've squashed some of those over time, but as the recent mallopt problem showed, there are still several lurking). Stefan