GNU bug report logs - #6979
In compilation buffer, 'gnu-include' rule is not working as intended

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6979 in the body.
You can then email your comments to 6979 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Pogonyshev <pogonyshev <at> gmx.net>
To: bug-gnu-emacs <at> gnu.org
Subject: In compilation buffer, 'gnu-include' rule is not working as intended
Date: Fri, 3 Sep 2010 22:18:03 +0300

[Message part 1 (text/plain, inline)]

Example file 'compilation.txt' claims it is supported to mark only the
last message as the error, skipping all 'included from...' lines,
which are often not interesting.  However, instead it marks all lines
except the first as errors.

To reproduce:

    M-x customize-variable
    compilation-error-regexp-alist

and follow the 'see also example file' link.

Screenshot of what I see is attached.

GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-09-02 on gonzo

Paul

[emacs-gcc-include.png (image/png, attachment)]

Message #8 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Paul Pogonyshev <pogonyshev <at> gmx.net>
To: 6979 <at> debbugs.gnu.org
Subject: More information
Date: Sat, 4 Sep 2010 16:57:40 +0300

I've found that 'gcc-include' rule is wrongly overriden by 'ruby': if
I disable the latter in 'compilation-error-regexp-alist', highlighting
is back to normal.  I'm not sure what a correct fix would be.  Maybe
ruby error highlighting should also highlight 'from' lines as info,
not errors.

Message #11 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Paul Pogonyshev <pogonyshev <at> gmx.net>
Cc: 6979 <at> debbugs.gnu.org
Subject: Re: bug#6979: More information
Date: Sat, 04 Sep 2010 14:54:45 -0400

Paul Pogonyshev <pogonyshev <at> gmx.net> writes:

> I've found that 'gcc-include' rule is wrongly overriden by 'ruby': if
> I disable the latter in 'compilation-error-regexp-alist', highlighting
> is back to normal.  I'm not sure what a correct fix would be.  Maybe
> ruby error highlighting should also highlight 'from' lines as info,
> not errors.

Could you please provide some examples?

Message #14 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Paul Pogonyshev <pogonyshev <at> gmx.net>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 6979 <at> debbugs.gnu.org
Subject: Re: bug#6979: More information
Date: Sat, 4 Sep 2010 22:06:41 +0300

Chong Yidong wrote:
> Paul Pogonyshev <pogonyshev <at> gmx.net> writes:
> 
> > I've found that 'gcc-include' rule is wrongly overriden by 'ruby': if
> > I disable the latter in 'compilation-error-regexp-alist', highlighting
> > is back to normal.  I'm not sure what a correct fix would be.  Maybe
> > ruby error highlighting should also highlight 'from' lines as info,
> > not errors.
> 
> Could you please provide some examples?

As I wrote in my original mail:

> To reproduce:
>
>     M-x customize-variable
>     compilation-error-regexp-alist
>
> and follow the 'see also example file' link.

Look for the string 'gcc-include' in the example.  In description it
claims that the first two lines would be highlighted as information
and the last as error.  In reality, second line:

                 from /usr/include/c++/3.3/backward/iostream.h:31,

is also highlighted as an error because it is handled by 'ruby' rule.

I would also argue that _all three_ lines should be information
because real error follows those, but that is a different issue.

Paul

Message #17 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Paul Pogonyshev <pogonyshev <at> gmx.net>
Cc: 6979 <at> debbugs.gnu.org
Subject: Re: bug#6979: More information
Date: Wed, 15 Sep 2010 23:57:00 -0400

I imagine this (likewise bug#6966?) has been fixed by the 2010-09-04
change to compile.el, could you confirm?

Message #20 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Paul Pogonyshev <pogonyshev <at> gmx.net>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 6979 <at> debbugs.gnu.org
Subject: Re: bug#6979: More information
Date: Thu, 16 Sep 2010 21:35:31 +0300

Glenn Morris wrote:
> I imagine this (likewise bug#6966?) has been fixed by the 2010-09-04
> change to compile.el, could you confirm?

Yes, it is fixed, but I don't know how to close bugs in this system.

Paul

Message #23 received at 6979 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Pogonyshev <pogonyshev <at> gmx.net>
Cc: rgm <at> gnu.org, 6979 <at> debbugs.gnu.org
Subject: Re: bug#6979: More information
Date: Thu, 16 Sep 2010 20:43:01 +0200

> From: Paul Pogonyshev <pogonyshev <at> gmx.net>
> Date: Thu, 16 Sep 2010 21:35:31 +0300
> Cc: 6979 <at> debbugs.gnu.org
> 
> Glenn Morris wrote:
> > I imagine this (likewise bug#6966?) has been fixed by the 2010-09-04
> > change to compile.el, could you confirm?
> 
> Yes, it is fixed, but I don't know how to close bugs in this system.

Reply to 6979-done <at> debbugs.gnu.org to cause bug #6979 be closed.

Previous Next

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