Re: How to stop find-grep-dired?

[Lennart Borgman]

David Kastrup wrote:
> > Why not have this behaviour for async processes too then?
> >     
>
> I seem to remember that I already provided an answer to the question.
>   
Maybe I misunderstood you, but was the reason not the ambiguity?

>   
> > Ambiguoties 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.  
You can still cancel the prompt with my solution.

At least that is the case when it works. There is something strange 
going on when I test my solution. Sometimes it seems like C-g still just 
runs keyboard-quit. I do not really understand why. Is it not possible 
to rebind C-g?

Another problem perhaps. If C-g is bound to keyboard-quit I get messages 
like this in the message buffer:

   QuitError during redisplay: (quit)
   Error during redisplay: (quit)

> 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.
>   
The advantage is that the user just have to remember C-g.

> 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.
>   
I agree with the principle but I would prefer C-g for similar reasons.