From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: interaction with "internal" emacs processes.
Date: Tue, 11 Oct 2005 17:02:50 +0200 [thread overview]
Message-ID: <7epsqcp04l.fsf@ada2.unipv.it> (raw)
In-Reply-To: 1128704816.772572.290360@f14g2000cwb.googlegroups.com
"rgb" <rbielaws@i1.net> writes:
> How is it possible that any function f-b could execute
> before f-a completes.
probably it was a typo (posting-grade code). anyway, "completes" is
insufficient to describe asynchronous operation, for which there is one
starting point, but multiple ending points; the programmer can control
the interaction of the ending points in various ways.
thi
next prev parent reply other threads:[~2005-10-11 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 15:44 interaction with "internal" emacs processes mak kwak
2005-10-06 16:25 ` Friedrich Laher
2005-10-06 17:56 ` Kevin Rodgers
[not found] ` <mailman.10118.1128621534.20277.help-gnu-emacs@gnu.org>
2005-10-07 17:06 ` rgb
2005-10-11 15:02 ` Thien-Thi Nguyen [this message]
2005-10-11 3:56 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2005-10-07 14:19 mak kwak
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=7epsqcp04l.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).