Re: Checking Process Status

[Jay Belanger <belanger@truman.edu>]

Kevin Rodgers <kevin.rodgers@ihs.com> writes:

> Eli Zaretskii wrote:
>
>> On Mon, 10 Feb 2003, Kevin Rodgers wrote:
>>>Jay Belanger wrote:
>>>>Kevin Rodgers wrote:
>
>>>>>Then force M-x compile to run the command synchronously:
>>>>>
>>>>>(fmakunbound 'start-process)
>>>>>
>>>>If I try that here (not with M-x compile), I get the message
>>>>"Multi-processing is not supported for this system"
>>>>(RedHat 8.0 with CVS emacs)
>>>>
>>>That is one of the undesirable consequences I alluded to.
>> Might as well be a bug in compile.el: sounds like some of its
>> condition to run the synchronous path are based on system-type, not
>> on start-process being not fboundp.  Perhaps this should be reported
>> as a bug.
>
> I thought that when Jay wrote "not with M-x compile", he meant that some other
> package that _requires_ asynchronous subprocess support had signalled the error.

Yeah, that's what I meant.
It was probably a dissimilar enough situation that that 
(fmakunbound 'start-process)
wasn't supposed to apply.
At any rate, Kevin's advice
> Is a nil TIMEOUT interpreted by accept-process-output as 0 or infinity?  If
> it's 0, try specifying a really large value (like most-positive-fixnum), or
> calling it in a loop.
seems to work, using
(accept-process-output myprocess 1000)
instead of
(accept-process-output myprocess)
seems to work.  
Thanks!

Jay