|
From: | GNU bug Tracking System |
Subject: | [Emacs-bug-tracker] bug#2144: closed (23.0.60; find-grep reports nonsense when interrupted) |
Date: | Sun, 10 Jul 2011 01:04:02 +0000 |
Your message dated Sat, 09 Jul 2011 21:03:43 -0400 with message-id <address@hidden> and subject line Re: 23.0.60; find-grep reports nonsense when interrupted has caused the GNU bug report #2144, regarding 23.0.60; find-grep reports nonsense when interrupted to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 2144: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2144 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: 23.0.60; find-grep reports nonsense when interrupted Date: Mon, 2 Feb 2009 01:55:05 +0100 Hello!When I let find-grep search for a pattern *and* it has already found and listed some in *grep* buffer and I then kill the process with C-c C-k, find-grep reports "[no match]" in mode-line. The buffer contains at the end:Grep finished with no matches found at <some date> This is almost true ... -- Greetings Pete There's no place like 127.0.0.1 – origin unknown
--- End Message ---
--- Begin Message ---Subject: Re: 23.0.60; find-grep reports nonsense when interrupted Date: Sat, 09 Jul 2011 21:03:43 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) Glenn Morris wrote: > Can't reproduce this: > > grep --version > GNU grep 2.5.3 > > Grep exited abnormally with code 130 at Wed Feb 25 00:27:36 > Grep:exit [130] > > Perhaps a buggy grep that exits with status 1 in case of error? > > man grep: > > POSIX only mandates, for programs such as grep, cmp, and diff, that > the exit status in case of error be greater than 1
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |