From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
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
Subject: Re: bug#141: Process sentinel not called in batch mode
Date: Fri, 16 May 2008 15:24:04 -0400 [thread overview]
Message-ID: <jwvabiq5a0d.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <uod76hxsc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 May 2008 22:08:35 +0300")
>> >> 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?
>>
>> I don't follow: we're talking about when should
>> wait_reading_process_output check status_notify.
>>
>> So to repeat/rephrase my question: why doesn't
>> wait_reading_process_output call status_notify when it is passed a zero
>> do_display?
> Sorry, let me explain my line of thought in more detail: Emacs only
> does a redisplay when it is idle. Emacs also checks input from
> subprocesses when it is idle. If we are not in redisplay, it means
> Emacs is not idle, and so it makes sense not to check for subprocess
> output at that time.
> Does this make any sense?
But if we're in wait_reading_process_output, that means that idle or
not, we're checking for process output, so why not check for process
status changes as well?
Stefan
next prev parent reply other threads:[~2008-05-16 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hcd1kcmz.fsf@stupidchicken.com>
2008-05-14 14:18 ` bug#141: Process sentinel not called in batch mode Stefan Monnier
[not found] ` <jwvy76d7yw2.fsf-monnier+emacsbugreports@gnu.org>
2008-05-16 11:32 ` Richard M Stallman
2008-05-16 13:25 ` Stefan Monnier
2008-05-16 14:41 ` Eli Zaretskii
2008-05-16 16:57 ` Stefan Monnier
2008-05-16 17:23 ` Chong Yidong
2008-05-16 19:08 ` Eli Zaretskii
2008-05-16 19:24 ` Stefan Monnier [this message]
2008-05-16 20:07 ` Eli Zaretskii
2008-05-18 3:45 ` Stefan Monnier
2008-05-19 3:00 ` Chong Yidong
2008-05-19 8:24 ` Stefan Monnier
2008-05-16 20:58 ` David Kastrup
2008-05-13 23:28 Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvabiq5a0d.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=141@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=bug-submit-list@donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).