From: Kevin Rodgers <kevin.rodgers@ihs.com>
Subject: Re: Checking Process Status
Date: Mon, 10 Feb 2003 13:47:18 -0700 [thread overview]
Message-ID: <3E480FD6.6040303@ihs.com> (raw)
In-Reply-To: m3el6ovu7x.fsf@vh213602.truman.edu
Jay Belanger wrote:
> Kevin Rodgers <kevin.rodgers@ihs.com> writes:
>>CarlC wrote:
>>>Understood. My concern is that this routine is going to possibly open a new
>>>buffer, and change point. I didn't want the user to wander around during the
>>>compile and then have emacs zap him a new screen. I will take your advice
>>>into consideration.
>>>
>>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.
> I have problem slightly similar to CarlC's, though.
> I need a program to stop at a certain point, and wait until a
> comint-process gives some output, and then and only then continue.
> (Also, the user shouldn't be able to move the point...)
> I thought accept-process-output would do that, but that doesn't seem
> to work. What should work?
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.
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
next prev parent reply other threads:[~2003-02-10 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 14:53 Checking Process Status 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 [this message]
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
[not found] <mailman.1775.1044945429.21513.help-gnu-emacs@gnu.org>
2003-02-12 0:10 ` Kevin Rodgers
2003-02-12 17:37 ` Jay Belanger
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=3E480FD6.6040303@ihs.com \
--to=kevin.rodgers@ihs.com \
/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).