unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jay Belanger <belanger@truman.edu>
Subject: Re: Checking Process Status
Date: Wed, 12 Feb 2003 11:37:45 -0600	[thread overview]
Message-ID: <m3ptpxv1qu.fsf@vh213602.truman.edu> (raw)
In-Reply-To: 3E49910F.8090208@ihs.com


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

  reply	other threads:[~2003-02-12 17:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1775.1044945429.21513.help-gnu-emacs@gnu.org>
2003-02-12  0:10 ` Checking Process Status Kevin Rodgers
2003-02-12 17:37   ` Jay Belanger [this message]
2003-02-03 14:53 CarlC
2003-02-03 15:04 ` David Kastrup
2003-02-03 17:49   ` Kevin Rodgers
2003-02-03 22:19     ` CarlC
2003-02-03 22:15   ` CarlC
2003-02-03 22:29     ` David Kastrup
2003-02-03 22:42       ` CarlC
2003-02-03 23:56         ` Kevin Rodgers
2003-02-04 17:20           ` Jay Belanger
2003-02-10 20:47             ` Kevin Rodgers
2003-02-11  6:35               ` Eli Zaretskii
2003-02-12 22:03           ` CarlC
     [not found]             ` <qWz2a.39840$yn1.1668284@twister.austin.rr.com>
2003-02-12 22:43               ` David Kastrup
2003-02-12 22:55                 ` CarlC
2003-02-12 23:17                   ` David Kastrup
2003-02-13  9:37                   ` Kai Großjohann

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=m3ptpxv1qu.fsf@vh213602.truman.edu \
    --to=belanger@truman.edu \
    /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.
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).