From: Dan Nicolaescu <dann@ics.uci.edu>
To: Vinicius Jose Latorre <viniciusjl@ig.com.br>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [user42@zip.com.au: compilation regexps for perl and weblint]
Date: Mon, 12 Nov 2007 09:55:55 -0800 [thread overview]
Message-ID: <ur94pfrqrf8.fsf@mothra.ics.uci.edu> (raw)
In-Reply-To: <473891EB.3070003@ig.com.br> (Vinicius Jose Latorre's message of "Mon, 12 Nov 2007 14:48:27 -0300")
Vinicius Jose Latorre <viniciusjl@ig.com.br> writes:
> Dan Nicolaescu wrote:
> > Vinicius Jose Latorre <viniciusjl@ig.com.br> writes:
> >
> > > Richard Stallman wrote:
> > > > Would someone please install these error patterns in the trunk,
> > > > if they are correct? (I cannot tell if they are correct.)
> > > >
> > > > We have papers from Kevin Ryde.
> > > > > > Installed in the trunk.
> >
> > Both new files do something like:
> >
> > ;;;###autoload (eval-after-load "compile" '(require 'compilation-perl))
> >
> > the goal is just to add some patterns to
> > compilation-error-regexp-alist*.
> >
> > Isn't this ugly?
> >
> > For an outside package this is OK. But IMHO when including this stuff
> > in emacs it might be a better idea to just add the patterns to
> > compile.el and be done with it.
> >
>
>
> Is there any problem if I just installed the patterns
> into compile.el as Dan suggests?
When you add the patterns to compile.el, can you please add
corresponding entries to etc/compilation.txt ?
next prev parent reply other threads:[~2007-11-12 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 9:02 [user42@zip.com.au: compilation regexps for perl and weblint] Richard Stallman
2007-11-12 4:03 ` Vinicius Jose Latorre
2007-11-12 4:01 ` Dan Nicolaescu
2007-11-12 17:18 ` Richard Stallman
2007-11-12 17:48 ` Vinicius Jose Latorre
2007-11-12 17:52 ` Vinicius Jose Latorre
2007-11-12 17:55 ` Dan Nicolaescu [this message]
2007-11-12 19:29 ` Vinicius Jose Latorre
2007-11-14 9:10 ` Glenn Morris
2007-12-29 0:52 ` Kevin Ryde
2008-01-08 8:03 ` Glenn Morris
2008-01-21 20:45 ` Kevin Ryde
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=ur94pfrqrf8.fsf@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=viniciusjl@ig.com.br \
/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.