From: Rajsekar Manokaran <rajsekar@gmail.com>
Subject: Re: compile.el does not find errors in numeric filenames
Date: Sun, 6 Feb 2005 11:03:22 +0530 [thread overview]
Message-ID: <9bec9e400502052133670b229c@mail.gmail.com> (raw)
In-Reply-To: <9bec9e4005020506506e75cf86@mail.gmail.com>
i debugged the problem.
the regexp was this
(gnu
"^\\(?:[[:alpha:]][-[:alnum:].]+: ?\\)?\
\\([/.]*[a-zA-Z]:?[^ \t\n:]*\\|{standard input}\\): ?\
\\([0-9]+\\)\\([.:]?\\)\\([0-9]+\\)?\
\\(?:-\\(?:\\([0-9]+\\)\\3\\)?\\.?\\([0-9]+\\)?\\)?:\
\\(?: *\\(\\(?:Future\\|Runtime\\)?[Ww]arning\\|W:\\)\\|\
*\\([Ii]nfo\\(?:\\>\\|rmationa?l?\\)\\|I:\\)\\)?"
1 (2 . 5) (4 . 6) (7 . 8))
and i changed it to
(gnu
"^\\(?:[[:alpha:]][-[:alnum:].]+: ?\\)?\
\\([/.]*[[:alnum:]]:?[^ \t\n:]*\\|{standard input}\\): ?\
\\([0-9]+\\)\\([.:]?\\)\\([0-9]+\\)?\
\\(?:-\\(?:\\([0-9]+\\)\\3\\)?\\.?\\([0-9]+\\)?\\)?:\
\\(?: *\\(\\(?:Future\\|Runtime\\)?[Ww]arning\\|W:\\)\\|\
*\\([Ii]nfo\\(?:\\>\\|rmationa?l?\\)\\|I:\\)\\)?"
1 (2 . 5) (4 . 6) (7 . 8))
I am also copying a diff file
please try it out and comment on it
diff -Naur old/compile.el new/compile.el
--- old/compile.el 2005-02-04 11:18:41.148180000 +0530
+++ new/compile.el 2005-02-04 11:18:13.099444056 +0530
@@ -214,7 +214,7 @@
(gnu
"^\\(?:[[:alpha:]][-[:alnum:].]+: ?\\)?\
-\\([/.]*[a-zA-Z]:?[^ \t\n:]*\\|{standard input}\\): ?\
+\\([/.]*[[:alnum:]]:?[^ \t\n:]*\\|{standard input}\\): ?\
\\([0-9]+\\)\\([.:]?\\)\\([0-9]+\\)?\
\\(?:-\\(?:\\([0-9]+\\)\\3\\)?\\.?\\([0-9]+\\)?\\)?:\
\\(?: *\\(\\(?:Future\\|Runtime\\)?[Ww]arning\\|W:\\)\\|\
On Sat, 5 Feb 2005 20:20:51 +0530, Rajsekar Manokaran
<rajsekar@gmail.com> wrote:
> Sending this mail again coz i have not got any reply and something
> tells me i sent this message before having got the reply from the
> listbot.
>
>
> I have a CVS version of emacs (checked out somewhere last week).
>
> I have a file with name like 10776.cc and compile.el does not
> recognize the output as errors.
> Then I changed the filename to a10776.cc and it worked
>
> i think one of the regexp in compilation-error-regexp-alist-alist
> is not setup correctly
>
> could some help me out ?
>
next prev parent reply other threads:[~2005-02-06 5:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 4:59 compile.el does not find errors in numeric filenames Rajsekar Manokaran
2005-02-04 5:50 ` Rajsekar Manokaran
2005-02-05 14:50 ` Fwd: " Rajsekar Manokaran
2005-02-06 5:33 ` Rajsekar Manokaran [this message]
2005-02-06 12:42 ` Richard Stallman
2005-02-06 13:39 ` Rajsekar Manokaran
2005-02-06 15:41 ` Andreas Schwab
2005-02-06 19:12 ` Rajsekar Manokaran
2005-02-06 20:29 ` Rajsekar Manokaran
2005-02-06 20:53 ` Andreas Schwab
2005-02-07 9:18 ` Richard Stallman
2005-02-07 10:19 ` Andreas Schwab
2005-02-07 14:37 ` Rajsekar
2005-02-07 20:16 ` Eli Zaretskii
2005-02-07 21:07 ` Rajsekar
2005-02-08 11:46 ` Richard Stallman
2005-02-09 21:46 ` Rajsekar
2005-02-06 15:55 ` Stefan Monnier
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=9bec9e400502052133670b229c@mail.gmail.com \
--to=rajsekar@gmail.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 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).