unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Reto Zimmermann <Reto.Zimmermann@synopsys.com>,
	Daniel Pfeiffer <occitan@esperanto.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: new compile.el
Date: Wed, 11 Mar 2009 10:46:01 -0400	[thread overview]
Message-ID: <jwv7i2wp1w8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <49B7BF5D.8090909@synopsys.com> (Reto Zimmermann's message of "Wed, 11 Mar 2009 14:40:45 +0100")

>> 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 compilation buffer.
> Looks like that's the problem.  It worked before though.

You mean in Emacs-21, right?  compile.el hasn't been changed much in
Emacs-23, IIRC.

Indeed, I now see that Emacs-21's compile.el explicitly copied the
error-regexp-alist setting from the calling buffer to the
compilation buffer.  I guess it might make sense to do that as well in
the new compile.el.  Daniel, could you look into it?

> Now variable compilation-file-regexp-alist also doesn't exist anymore,
> so I guess I would have to rewrite the whole compilation section of
> vhdl-mode.

IIRC you can just place the corresponding entries onto
compilation-error-regexp-alist.


        Stefan




  reply	other threads:[~2009-03-11 14:46 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
2009-03-11 13:40           ` Reto Zimmermann
2009-03-11 14:46             ` Stefan Monnier [this message]
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=jwv7i2wp1w8.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=Reto.Zimmermann@synopsys.com \
    --cc=emacs-devel@gnu.org \
    --cc=occitan@esperanto.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).