rgrep breakage

rgrep breakage

[Sam Steingold]

GNU Emacs 24.0.50.7 (x86_64-unknown-linux-gnu, GTK+ Version 2.10.4)
 of 2011-02-02 on tbox

after rgrep terminates, I am immediately prompted to jump to a
non-existent file:

Find this grep hit in (default Grep started at Wed Feb  2 09): ......

Debugger entered--Lisp error: (quit)
  completing-read("Find this grep hit in (default Grep started at Wed Feb  2 09): " read-file-name-internal file-exists-p t "...path...." file-name-history "Grep started at Wed Feb  2 09")
  read-file-name("Find this grep hit in (default Grep started at Wed Feb  2 09): " "...path...." "Grep started at Wed Feb  2 09" t nil)
  compilation-find-file(#<marker at 66 in *grep*> "Grep started at Wed Feb  2 09" nil)
  compilation-next-error-function(0 nil)
  next-error-internal()
  compile-goto-error()
  compilation-auto-jump(#<buffer *grep*> 66)
  apply(compilation-auto-jump (#<buffer *grep*> 66))
  byte-code("r\301\b\302H\b\303H\"\210)\301\207" [timer apply 5 6] 4)
  timer-event-handler([t 19785 29013 973959 nil compilation-auto-jump (#<buffer *grep*> 66) nil])

grep buffer looks like this:

-*- mode: grep; default-directory: "...path...." -*-
Grep started at Wed Feb  2 09:59:33

find . ......
... some matches ....

Grep finished (matches found) at Wed Feb  2 09:59:34


-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://iris.org.il http://jihadwatch.org http://dhimmi.com
http://ffii.org http://truepeace.org http://memri.org
Two wrongs don't make a right, but three rights make a left.

grep breakage

[Sam Steingold]

emacs -Q
(setq compilation-auto-jump-to-first-error t)
M-x grep RET foo bar RET

==>
echo area:
Grep exited abnormally with code 2

minibuffer:
Find this grep hit in (default Grep started at Tue Feb  8 18): ~/

*grep* buffer:
the left fringe arrow points to the second line in the buffer:
Grep started at Tue Feb  8 18:56:45


even without compilation-auto-jump-to-first-error, you can use
compilation-next-error to see that grep thinks that "Grep started..." is
the first match.


-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://www.memritv.org http://ffii.org http://www.PetitionOnline.com/tap12009/
http://iris.org.il http://mideasttruth.com http://jihadwatch.org
There is an exception to every rule, including this one.

Re: grep breakage

[Glenn Morris]

Already reported to the correct place, namely the bug list.

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8004

Re: grep breakage

[Sam Steingold]

> * Glenn Morris <etz@tah.bet> [2011-02-08 19:02:29 -0500]:
>
> Already reported to the correct place, namely the bug list.
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8004

I thought that the bug tracker was for the released versions.


-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://honestreporting.com http://iris.org.il http://jihadwatch.org
http://ffii.org http://www.PetitionOnline.com/tap12009/
OK, so you're a Ph.D.  Just don't touch anything.

Re: grep breakage

[Chong Yidong]

Sam Steingold <sds@gnu.org> writes:

>> * Glenn Morris <etz@tah.bet> [2011-02-08 19:02:29 -0500]:
>>
>> Already reported to the correct place, namely the bug list.
>>
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8004
>
> I thought that the bug tracker was for the released versions.

Nope, the same rationale applies to using the bug tracker for the
development and released versions.

Re: grep breakage

[Sam Steingold]

> * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2011-02-09 11:04:51 -0500]:
>
>> I thought that the bug tracker was for the released versions.
>
> Nope, the same rationale applies to using the bug tracker for the
> development and released versions.

should I report the global.h windows issue of this morning to the bug
tracker?

-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://www.memritv.org http://dhimmi.com http://memri.org
http://pmw.org.il http://camera.org http://www.PetitionOnline.com/tap12009/
Never trust a man who can count to 1024 on his fingers.

Re: grep breakage

[Glenn Morris]

Sam Steingold wrote:

> should I report the global.h windows issue of this morning to the bug
> tracker?

If it works as these things usually do, at least one person will do that
pretty soon... But a "doesn't build" problem is unlikely to get
forgotten about, so IMO now that it has been mentioned there is no need
for a bug report in this case.

Re: grep breakage

[Eli Zaretskii]

> From: Sam Steingold <sds@gnu.org>
> Date: Wed, 09 Feb 2011 11:28:10 -0500
> 
> > * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2011-02-09 11:04:51 -0500]:
> >
> >> I thought that the bug tracker was for the released versions.
> >
> > Nope, the same rationale applies to using the bug tracker for the
> > development and released versions.
> 
> should I report the global.h windows issue of this morning to the bug
> tracker?

No, it doesn't make sense to use the bug tracker for such transient
problems.

Re: grep breakage

[Sam Steingold]

> * Eli Zaretskii <ryvm@tah.bet> [2011-02-09 21:24:45 +0200]:
>> 
>> > * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2011-02-09 11:04:51 -0500]:
>> >
>> >> I thought that the bug tracker was for the released versions.
>> >
>> > Nope, the same rationale applies to using the bug tracker for the
>> > development and released versions.
>> 
>> should I report the global.h windows issue of this morning to the bug
>> tracker?
>
> No, it doesn't make sense to use the bug tracker for such transient
> problems.

Now I am _eminently_ confused.
 :-(

-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://www.PetitionOnline.com/tap12009/ http://truepeace.org http://pmw.org.il
http://thereligionofpeace.com http://honestreporting.com http://memri.org
Let us remember that ours is a nation of lawyers and order.

Re: grep breakage

[Eli Zaretskii]

> From: Sam Steingold <sds@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 09 Feb 2011 14:31:40 -0500
> 
> > * Eli Zaretskii <ryvm@tah.bet> [2011-02-09 21:24:45 +0200]:
> >> 
> >> > * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2011-02-09 11:04:51 -0500]:
> >> >
> >> >> I thought that the bug tracker was for the released versions.
> >> >
> >> > Nope, the same rationale applies to using the bug tracker for the
> >> > development and released versions.
> >> 
> >> should I report the global.h windows issue of this morning to the bug
> >> tracker?
> >
> > No, it doesn't make sense to use the bug tracker for such transient
> > problems.
> 
> Now I am _eminently_ confused.
>  :-(

How can I help you with that confusion?

We simply don't use to report build breakages to the bug tracker.  All
the other bugs should be reported there.