From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: Processus delay
Date: 30 Apr 2004 15:08:13 +0200 [thread overview]
Message-ID: <7e1xm5y5oi.fsf@ada2.unipv.it> (raw)
In-Reply-To: 20040430115528.306ea49d.vincent.barichard@info.univ-angers.fr
Vincent Barichard <vincent.barichard@info.univ-angers.fr> writes:
> Is anybody has an idea ??
you can study the system behavior by wrapping the subprocess w/
a script that saves the time when its child actually finishes.
then compare that time to the time reported by emacs. if these
differ by 2sec (as observed from macroscopic scale), that means
it is slow sentinel dispatch (but why we still don't know), as
you hypothesized.
thi
next prev parent reply other threads:[~2004-04-30 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 9:55 Processus delay Vincent Barichard
2004-04-30 13:08 ` Thien-Thi Nguyen [this message]
2004-04-30 21:09 ` Stefan Monnier
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=7e1xm5y5oi.fsf@ada2.unipv.it \
--to=ttn@glug.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).