From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Reto Zimmermann <Reto.Zimmermann@synopsys.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: new compile.el
Date: Tue, 10 Mar 2009 10:47:27 -0400 [thread overview]
Message-ID: <jwvocw9igpv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <49B66A32.20908@synopsys.com> (Reto Zimmermann's message of "Tue, 10 Mar 2009 14:25:06 +0100")
>> How do you set the alist? With the new code, the alist is not used
>> directly, but instead it's "compiled" to a set of font-lock-keywords
>> rules, so if you change it after "compilation" it won't take effect.
> The alist is assigned before the first time "compile" is called. So not at
> startup but only when the user calls "compile" for the first time.
I'm guessing that you're talking about the error-regexp code that's in
emacs/lisp/progmodes/vhdl-mode.el. Looking at it, I do not quite
understand what the code is meant to do:
vhdl-compile-use-local-error-regexp sets error-regexp-alist in the
vhdl-mode buffer rather than in the compilaiton buffer.
I.e. please reproduce the problem and then in the compilation buffer,
check the value of compilation-error-regexp-alist (and if it looks
correct, check the value of font-lock-keywords as well: even if you're
not familiar with it, you should be able to recognize some parts,
e.g. the fact that each entry in compilation-error-regexp-alist should
have a corresponding entry in font-lock-keywords).
Stefan
next prev parent reply other threads:[~2009-03-10 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 12:48 new compile.el Reto Zimmermann
2009-03-06 22:24 ` Stefan Monnier
2009-03-06 22:41 ` Reto Zimmermann
2009-03-10 2:26 ` Stefan Monnier
2009-03-10 13:25 ` Reto Zimmermann
2009-03-10 14:47 ` Stefan Monnier [this message]
2009-03-11 13:40 ` Reto Zimmermann
2009-03-11 14:46 ` Stefan Monnier
2009-03-13 12:46 ` Reto Zimmermann
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=jwvocw9igpv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Reto.Zimmermann@synopsys.com \
--cc=emacs-devel@gnu.org \
/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).