GNU bug report logs - #2144
23.0.60; find-grep reports nonsense when interrupted

Previous Next

Package: emacs;

Reported by: Peter Dyballa <Peter_Dyballa <at> Web.DE>

Date: Mon, 2 Feb 2009 01:00:02 UTC

Severity: normal

Tags: moreinfo, unreproducible

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Glenn Morris <rgm <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#2144: closed (23.0.60; find-grep reports nonsense when
 interrupted)
Date: Sun, 10 Jul 2011 01:04:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sat, 09 Jul 2011 21:03:43 -0400
with message-id <9xhb6veykw.fsf <at> fencepost.gnu.org>
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
help-debbugs <at> gnu.org.)


-- 
2144: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2144
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Peter Dyballa <Peter_Dyballa <at> Web.DE>
To: emacs-pretest-bug <at> gnu.org
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





[Message part 3 (message/rfc822, inline)]
From: Glenn Morris <rgm <at> gnu.org>
To: 2144-done <at> debbugs.gnu.org
Subject: Re: 23.0.60; find-grep reports nonsense when interrupted
Date: Sat, 09 Jul 2011 21:03:43 -0400
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


This bug report was last modified 14 years and 39 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.