From: Chong Yidong <cyd@stupidchicken.com>
To: Kevin Ryde <user42@zip.com.au>
Cc: 3965@emacsbugs.donarmstrong.com
Subject: bug#3965: 23.1.50; compilation-mode gnu error regexp mismatching ant, irix, gcc-include
Date: Sun, 02 Aug 2009 18:46:59 -0400 [thread overview]
Message-ID: <87hbwpq1ek.fsf@cyd.mit.edu> (raw)
> Doing
>
> (setq compilation-error-regexp-alist '(gnu))
>
> and visiting etc/compilation.txt shows some mismatched parts.
>
> Under "ant" ...
> Under "irix"...
> And under "gcc-include"...
>
> With all patterns enabled `next-error' offers those wrong matches
> instead of what the specific patterns for those parts get -- I suppose
> because the gnu match is earlier in the line.
Correct. That's the intended behavior.
> My best idea for the irix ones would be to disallow ": " in the gnu
> pattern filename part. Other colons could be allowed for dos drive
> letters or the occasional filename with a colon, but rate colon+space as
> more likely to be a separator than a part of a name. Mind you the gnu
> pattern is already far too complicated for me to want to do anything to
> it :-)
There's no point changing the gnu pattern just to handle these
additional patterns, which already have their own dedicated entries in
compilation-error-regexp-alist.
next reply other threads:[~2009-08-02 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 22:46 Chong Yidong [this message]
2009-08-04 1:52 ` bug#3965: 23.1.50; compilation-mode gnu error regexp mismatching ant, irix, gcc-include Kevin Ryde
-- strict thread matches above, loose matches on Subject: below --
2009-07-29 23:13 Kevin Ryde
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbwpq1ek.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=3965@emacsbugs.donarmstrong.com \
--cc=user42@zip.com.au \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).