From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.emacs.bugs Subject: Re: bug#141: Process sentinel not called in batch mode Date: Fri, 16 May 2008 17:41:45 +0300 Message-ID: References: <87hcd1kcmz.fsf@stupidchicken.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1210948980 29504 80.91.229.12 (16 May 2008 14:43:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 May 2008 14:43:00 +0000 (UTC) Cc: 141@emacsbugs.donarmstrong.com, rms@gnu.org, cyd@stupidchicken.com, eller.helmut@gmail.com, emacs-devel@gnu.org, bug-submit-list@donarmstrong.com, bug-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 16 16:43:35 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 1Jx199-0002IR-UZ for ged-emacs-devel@m.gmane.org; Fri, 16 May 2008 16:43:00 +0200 Original-Received: from localhost ([127.0.0.1]:38168 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jx18Q-0002KL-HI for ged-emacs-devel@m.gmane.org; Fri, 16 May 2008 10:42:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jx184-0002BH-Sx for emacs-devel@gnu.org; Fri, 16 May 2008 10:41:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jx184-0002At-Be for emacs-devel@gnu.org; Fri, 16 May 2008 10:41:52 -0400 Original-Received: from [199.232.76.173] (port=51940 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jx183-0002A9-8F; Fri, 16 May 2008 10:41:51 -0400 Original-Received: from mtaout3.012.net.il ([84.95.2.7]:40927) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jx17z-0006ab-FU; Fri, 16 May 2008 10:41:47 -0400 Original-Received: from HOME-C4E4A596F7 ([83.130.255.47]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K0Y00GL4UTW7ZH2@i_mtaout3.012.net.il>; Fri, 16 May 2008 17:56:21 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:97272 gmane.emacs.bugs:18016 Archived-At: > From: Stefan Monnier > Date: Fri, 16 May 2008 09:25:54 -0400 > Cc: 141@emacsbugs.donarmstrong.com, cyd@stupidchicken.com, > eller.helmut@gmail.com, emacs-devel@gnu.org, > bug-submit-list@donarmstrong.com, bug-gnu-emacs@gnu.org > > >> This problem occurs because wait_reading_process_output only calls > >> status_notify when given a nonzero DO_DISPLAY argument (process.c:4451). > >> Although wait_reading_process_output is called from many places in > >> Emacs, it is given a nonzero DO_DISPLAY argument only during > >> kbd_buffer_get_event. But that function is never called in batch mode. > > > Does anyone know why we test do_display there? > > > I think the idea is, if you are going to update the display, it is > > good to display the fact that a process has terminated. > > This side I understand, but what about the other: why should we not > check process status in the case where we are not redisplaying? Because Emacs generally looks at process output only when it's idle?