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 12:47:44 +0200 [thread overview]
Message-ID: <85oduhknn3.fsf@lola.goethe.zz> (raw)
In-Reply-To: <44E6EA9F.7080700@student.lu.se> (Lennart Borgman's message of "Sat, 19 Aug 2006 12:40:31 +0200")
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
> It is BTW a bit hard to understand what "if you quit" means here,
> but it is described in "(elisp) Synchronous Processes" I see
> now. Maybe the doc string needs a bit more explanation?
>
> From this info node:
>
> While Emacs waits for the synchronous subprocess to terminate, the
> user can quit by typing `C-g'.
C-g is Emacs' way to trigger a `quit' signal.
> Why not have this behaviour for async processes too then?
I seem to remember that I already provided an answer to the question.
> Ambigouties can perhaps be removed by that little question I added
> to my suggestion in another message.
Any question like that is supposed to be abortable with C-g. It would
be a nuisance if that happened to stop the process. It would also
mean that the sequence to stop a process would need to be C-g y and I
don't see the advantage over C-c C-k.
There is a concern that we should probably unify on this key sequence:
for example, I have been bitten by C-c C-c actually killing a CVS
process.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-08-19 10:47 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
2006-08-19 10:40 ` Lennart Borgman
2006-08-19 10:47 ` David Kastrup [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85oduhknn3.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.