all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmx.net>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 6979@debbugs.gnu.org
Subject: bug#6979: More information
Date: Sat, 4 Sep 2010 22:06:41 +0300	[thread overview]
Message-ID: <201009042206.42465.pogonyshev@gmx.net> (raw)
In-Reply-To: <871v999w5m.fsf@stupidchicken.com>

Chong Yidong wrote:
> Paul Pogonyshev <pogonyshev@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





  reply	other threads:[~2010-09-04 19:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 19:18 bug#6979: In compilation buffer, 'gnu-include' rule is not working as intended Paul Pogonyshev
2010-09-04 13:57 ` bug#6979: More information Paul Pogonyshev
2010-09-04 18:54   ` Chong Yidong
2010-09-04 19:06     ` Paul Pogonyshev [this message]
2010-09-16  3:57       ` Glenn Morris
2010-09-16 18:35         ` Paul Pogonyshev
2010-09-16 18:43           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201009042206.42465.pogonyshev@gmx.net \
    --to=pogonyshev@gmx.net \
    --cc=6979@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.