From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: SYNC_INPUT and 23.1. Date: Tue, 11 Mar 2008 16:22:04 -0400 Message-ID: References: <47CE52B1.3050600@swipnet.se> <47D63FEE.1040807@swipnet.se> <47D655E7.6070108@gnu.org> <47D660BE.9040201@swipnet.se> <47D684B9.3020803@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1205266980 12567 80.91.229.12 (11 Mar 2008 20:23:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 11 Mar 2008 20:23:00 +0000 (UTC) Cc: Jan =?iso-8859-1?Q?Dj=1FFFFFFFFFFFFFFFrv?= , emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 11 21:23:19 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JZB02-0005ba-Bc for ged-emacs-devel@m.gmane.org; Tue, 11 Mar 2008 21:23:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JZAzT-0001HT-Rw for ged-emacs-devel@m.gmane.org; Tue, 11 Mar 2008 16:22:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JZAzQ-0001GF-20 for emacs-devel@gnu.org; Tue, 11 Mar 2008 16:22:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JZAzK-0001BN-Ut for emacs-devel@gnu.org; Tue, 11 Mar 2008 16:22:23 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JZAzK-0001BH-QL for emacs-devel@gnu.org; Tue, 11 Mar 2008 16:22:18 -0400 Original-Received: from mercure.iro.umontreal.ca ([132.204.24.67]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JZAzH-0005Mi-5K; Tue, 11 Mar 2008 16:22:15 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id EB25F2CFA21; Tue, 11 Mar 2008 16:22:14 -0400 (EDT) Original-Received: from faina.iro.umontreal.ca (faina.iro.umontreal.ca [132.204.26.177]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id DEDE83FE0; Tue, 11 Mar 2008 16:22:04 -0400 (EDT) Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id CC7946CAA2; Tue, 11 Mar 2008 16:22:04 -0400 (EDT) In-Reply-To: <47D684B9.3020803@gnu.org> (Jason Rumney's message of "Tue, 11 Mar 2008 13:10:17 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) 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=-2.82, requis 5, autolearn=not spam, ALL_TRUSTED -2.82) X-DIRO-MailScanner-From: monnier@iro.umontreal.ca X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:92185 Archived-At: >>>>> Are there any plans to make SYNC_INPUT the default for 23.1? >>>>> >>>>> That's a good idea. Any objection? >>>>> >>>> >>>> Sinc there has been no objections, I enabled this by default. You can >>>> pass --disable-sync-input to configure if there is problems. >>>> But I guess we soon will start take advantage of sync input so the >>>> disabled case will become obsolete. When we feel confident that sync >>>> input works, I'll remove the non-sync-input code. >>> >>> Is this just an X thing, or does it affect common code as well? Are there >>> changes we should be making on other platforms to support SYNC_INPUT? >>> >> I think Stefan can answer that best, AFAIK, he did the implementation. >> I assumed it was an X thing. Does other platforms use signals for the GUI >> loop? I must admint that I don't know what systems use what. The SNYC_INPUT code replaces the signal handlign code by a code that simply sets a flag and then lets a few macros like QUIT and UNBLOCK_INPUT run the real signal-handler code in case the flag is set. I.e. this runs the signal handler code synchronously rather than asynchronously. The main benefit is for malloc and friends. For systems that use a separate thread to handle GUI events, SYNC_INPUT should make no difference. Stefan