From: David Kastrup <dak@gnu.org>
Subject: Re: Checking Process Status
Date: 03 Feb 2003 23:29:52 +0100 [thread overview]
Message-ID: <x565s1ro9r.fsf@lola.goethe.zz> (raw)
In-Reply-To: URB%9.23663$2y.1199994@twister.austin.rr.com
"CarlC" <carlc@snowbd.com> writes:
> "David Kastrup" <dak@gnu.org> wrote in message
> news:x5wukhv20i.fsf@lola.goethe.zz...
> > Save the old value of the process' sentinel, enter your own function
> > there, and have that do its work as well as calling the saved
> > sentinel.
>
> Thanks for the quick response, David. I guess I need to know why
> this is the case. If I can get a process-status, why do I need to
> modify the compile sentinel. Does the existing sentinel wrap it up
> so that I can't access it's status? This doesn't appear to be the
> case when I am debugging. I can set a variable and view its status
> as "run". If I can do this, why can't I add a conditional to check
> this status outside of the sentinel? I just want to know if the
> compilation process is running. Thanks, again.
Your code programmed a busy wait. That's ugly, butt-ugly. Instead
just let your code be run when the process has finished. Anyhow, if
at all, you would need to compare to symbols 'run and 'exit, not
strings.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-02-03 22:29 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 [this message]
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
[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=x565s1ro9r.fsf@lola.goethe.zz \
--to=dak@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.
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).