grep gets confused if interrupted

grep gets confused if interrupted

[Dan Nicolaescu]

M-x lgrep RET setq RET el /PATH_TO_EMACS/lisp RET

(this should take enough time to allow you to switch to the *grep*
buffer and do C-c C-k)

Then grep prints at the end of the buffer:

Grep finished with no matches found

(there are plenty of matches in the buffer at that point)

Can someone please fix this?

Re: grep gets confused if interrupted

[Juri Linkov]

> M-x lgrep RET setq RET el /PATH_TO_EMACS/lisp RET
>
> (this should take enough time to allow you to switch to the *grep*
> buffer and do C-c C-k)
>
> Then grep prints at the end of the buffer:
>
> Grep finished with no matches found
>
> (there are plenty of matches in the buffer at that point)
>
> Can someone please fix this?

It tried this and it prints for me:

Grep interrupt at Mon Feb 25 23:45:11

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: grep gets confused if interrupted

[Dan Nicolaescu]

Juri Linkov <juri@jurta.org> writes:

  > > M-x lgrep RET setq RET el /PATH_TO_EMACS/lisp RET
  > >
  > > (this should take enough time to allow you to switch to the *grep*
  > > buffer and do C-c C-k)
  > >
  > > Then grep prints at the end of the buffer:
  > >
  > > Grep finished with no matches found
  > >
  > > (there are plenty of matches in the buffer at that point)
  > >
  > > Can someone please fix this?
  > 
  > It tried this and it prints for me:
  > 
  > Grep interrupt at Mon Feb 25 23:45:11

OK, it has to do with the SHELL: 
Grep prints this in the beginning:

grep -i -nH -e setq *.el
tcsh: No entry for terminal type "emacs-grep"
tcsh: using dumb terminal settings.


If I do: 
M-: (setq shell-file-name "/bin/sh") RET

then interrupting works as expected. 

This is on a Fedora 8 x86 system.