unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Arjan Bos <Arjan.Bos@nospam.ISeeYou.nl>
Subject: Re: Compilation error regexp alist doesn't match my compiler anymor
Date: Wed, 26 May 2004 00:33:22 +0200	[thread overview]
Message-ID: <c90hjm$h9v$1@reader13.wxs.nl> (raw)
In-Reply-To: <m3n03w71j1.fsf@eric.rossnet.com>

Michael Slass wrote:

> 
> ,----[ C-h v compilation-error-regexp-alist RET ]
> | compilation-error-regexp-alist's value is shown below.
> | 
> | Documentation:
> | Alist that specifies how to match errors in compiler output.
> | Each elt has the form (REGEXP FILE-IDX LINE-IDX [COLUMN-IDX FILE-FORMAT...])
> | If REGEXP matches, the FILE-IDX'th subexpression gives the file name, and
> | the LINE-IDX'th subexpression gives the line number.  If COLUMN-IDX is
> | given, the COLUMN-IDX'th subexpression gives the column number on that line.
> | If any FILE-FORMAT is given, each is a format string to produce a file name to
> | try; %s in the string is replaced by the text matching the FILE-IDX'th
> | subexpression.
> | 
> | Defined in `compile'.
> | 
> | Value:
> | <snip>
> `----
> 
> I don't know how much that has changed in the cvs version of emacs,
> but the explanation below should let you adapt.
> 
I know that it should be sufficient, but I never put enough effort in 
learning lists in lisp. But it has changed a lot since my previous 
snapshot (last march).


> So, you're pretty close: you've got a regex which captures your
> filename (and, incorrectly, the trailing colon) into subexp 1, and the
> line number in subexp 2.  You want to add an element to
> compilation-error-regexp-alist that includes your regex, the capture
> index of the filename, and the capture index of the line number, in
> that order:
> ( "^\\(.*\\.nrx\\):[ \\t]*\\([0-9]+\\)" 1 2)
>   --- note the colon moved outside the capture parens
Hmm, should have noticed that meself.
> 
> Then you want to add the little list above to the place where
> compile-mode will find it, compilation-error-regexp-alist.  You do
> that with a function called add-to-list
>   
> Try this:
> 
> (add-to-list
>  'compilation-error-regexp-alist
>  '("^\\(.*\\.nrx\\):[ \\t]*\\([0-9]+\\)" 1 2))
> 
> Make sense?
Yes, thanks a lot, the add-to-list form was missing from my lisp vocabulary.
It does indeed work now.

However, its new value is now (("^\\(.*\\.nrx\\):[ \\t]*\\([0-9]+\\)" 1 
2) absoft ada aix ant bash borland caml comma edg-1 edg-2 epc ...)

Where the names somehow point to entries in 
compilation-error-regexp-alist-alist. So I got lost in thinking that I 
should add a name in compilation-error-regexp-alist and the regexp in 
compilation-error-regexp-alist-alist.

Let's hope this current solution is future proof.
-- 
--
If you really want to contact me, then replace the "I see you" text by 
its three letter accronym, ICU.

Fabricate Diem PVNC, Motto of the Night Watch -- Terry Pratchett

  reply	other threads:[~2004-05-25 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 17:13 Compilation error regexp alist doesn't match my compiler anymor Arjan Bos
2004-05-25 19:24 ` Michael Slass
2004-05-25 22:33   ` Arjan Bos [this message]
2004-05-26 18:35 ` 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='c90hjm$h9v$1@reader13.wxs.nl' \
    --to=arjan.bos@nospam.iseeyou.nl \
    --cc=Arjan.Bos@ISeeYou.nl \
    /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.
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).