all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reto Zimmermann <Reto.Zimmermann@synopsys.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: new compile.el
Date: Tue, 10 Mar 2009 14:25:06 +0100	[thread overview]
Message-ID: <49B66A32.20908@synopsys.com> (raw)
In-Reply-To: <jwvd4cqjeqr.fsf-monnier+emacs@gnu.org>

>>>>How do I transition a major mode (vhdl-mode) to use the new
>>>>compile.el? From reading the compilation-error-regexp-alist
>>>>description it sounds like it should still work with the old alist
>>>>but then it doesn't work right.
>>>
>>>It should work.  Give us more details of the problems you encountered.
>>
>>Only error messages with a certain syntax ("<filename>:<linenumber>:") are
>>found and highlighted, but not others which should also match regexps
>>defined in the alist.  Just as if only one regexp from (the middle) of the
>>alist is active.  The same alist highlighted all errors with the old
>>compile.el.
> 
> 
> 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.

Reto





  reply	other threads:[~2009-03-10 13:25 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 [this message]
2009-03-10 14:47         ` Stefan Monnier
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

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

  git send-email \
    --in-reply-to=49B66A32.20908@synopsys.com \
    --to=reto.zimmermann@synopsys.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.