From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: How to stop find-grep-dired?
Date: Sat, 19 Aug 2006 10:49:01 +0200 [thread overview]
Message-ID: <851wrdm7pe.fsf@lola.goethe.zz> (raw)
In-Reply-To: <44E6CDA5.3080102@student.lu.se> (Lennart Borgman's message of "Sat, 19 Aug 2006 10:36:53 +0200")
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
> David Kastrup wrote:
>> Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>>
>>
>>> BTW, how do you see if a process is asynchronous?
>>>
>>
>> Emacs couldn't update the window otherwise.
>>
> Yes, but how do you know that the process is async from elisp? Or is
> that maybe just a stupid question .... ;-)
Because of the way is was started. call-process starts synchronous
processes (with the exception of a 0 argument for BUFFER, in which
case the process is detached), start-process starts asynchronous
processes.
> I was just thinking about stopping sync processes. Could that be done
> with C-g (maybe rewritten)?
The doc string for start-process already states
If BUFFER is 0, `call-process' returns immediately with value nil.
Otherwise it waits for PROGRAM to terminate and returns a numeric
exit status or a signal description string. If you quit, the
process is killed with SIGINT, or SIGKILL if you quit again.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-08-19 8:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 15:20 How to stop find-grep-dired? Lennart Borgman
2006-08-19 4:35 ` Richard Stallman
2006-08-19 7:40 ` Lennart Borgman
2006-08-19 7:45 ` David Kastrup
2006-08-19 8:09 ` Lennart Borgman
2006-08-19 8:28 ` David Kastrup
2006-08-19 8:36 ` Lennart Borgman
2006-08-19 8:49 ` David Kastrup [this message]
2006-08-19 10:40 ` Lennart Borgman
2006-08-19 10:47 ` David Kastrup
2006-08-19 14:53 ` Lennart Borgman
2006-08-19 15:04 ` David Kastrup
2006-08-19 15:18 ` Lennart Borgman
2006-08-20 4:32 ` Richard Stallman
2006-08-21 18:40 ` Stuart D. Herring
2006-08-21 23:40 ` Lennart Borgman
2006-08-20 4:32 ` Richard Stallman
2006-08-21 8:56 ` Ehud Karni
2006-08-21 9:14 ` Lennart Borgman
2006-08-22 3:09 ` Richard Stallman
2006-08-22 5:44 ` Lennart Borgman
2006-08-22 5:59 ` Drew Adams
2006-08-22 7:21 ` Lennart Borgman
2006-08-22 15:41 ` Richard Stallman
2006-08-22 15:52 ` Andreas Schwab
2006-08-22 16:31 ` Lennart Borgman
2006-08-24 6:12 ` Lennart Borgman
2006-08-23 4:06 ` Richard Stallman
2006-08-29 22:04 ` Juri Linkov
2006-08-30 17:58 ` Richard Stallman
2006-08-30 21:16 ` Stefan Monnier
2006-08-31 7:43 ` Kim F. Storm
2006-08-31 18:16 ` Richard Stallman
2006-08-31 18:49 ` David Kastrup
2006-08-31 23:34 ` Juri Linkov
2006-09-01 2:10 ` Miles Bader
2006-09-01 23:47 ` Juri Linkov
2006-08-30 22:46 ` Juri Linkov
2006-08-21 9:15 ` Lennart Borgman
2006-08-22 3:09 ` Richard Stallman
2006-08-19 8:44 ` Andreas Schwab
2006-08-19 10:33 ` Lennart Borgman
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=851wrdm7pe.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).