Re: Can't stop find-grep-dired when using Cygwin for the inferior process

[Lennart Borgman]

Kim F. Storm wrote:
> Lennart Borgman <address@hidden> writes:
>
>   
> > Lennart Borgman wrote:
> >     
> > > Andreas Schwab wrote:
> > >       
> > > > Richard Stallman <address@hidden> writes:
> > > >
> > > >  
> > > >         
> > > > > I see C-c C-k already has that meaning in the buffers made by M-x grep
> > > > > and M-x compile.  So let's set it up to kill the process of
> > > > > find-grep-dired as well.
> > > > >     
> > > > >           
> > > > It already does.
> > > >
> > > > Andreas.
> > > >   
> > > >         
> > > Thanks. I did not notice and now I know why. When using Cygwin for
> > > the inferior process trying to use kill-find just hangs Emacs. So
> > > there is a bug here.
> > >
> > > kill-find now uses `delete-process'. Using `interrupt-process' or
> > > kill-process' works instead. Is there any reason not to use them? Or
> > > at least try them first?
> > >
> > > Maybe a process killing command should try this one after the other
> > > until the process is gone? (And then do the mode specific cleanup.)
> > >       
>
> Can you propose a specific change that works on cygwin, so we can try
> it on other platforms (or just make it specific to cygwin)?
>   
As I wrote both interrupt-process and kill-process works in my case 
here. However I do not know exactly what they do (cleanup etc).

There seem to be another bug on w32 too. I just tried using CMD.EXE for 
the inferior process instead. That does not seem to work at all. I got this:

 d:/ecvs/:
 find . \( -type f -exec grep -q -e "message" {} \;  \) -exec ls -ld {} \;
 find: missing argument to `-exec'

 find exited abnormally with code 1 at Sun Aug 27 00:16:20