From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: compilation-error-regexp-alist syntax problems
Date: Wed, 04 Feb 2004 14:50:21 GMT [thread overview]
Message-ID: <jwvy8rizytg.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca> (raw)
In-Reply-To: 40202108.7060308@yahoo.com
> I don't understand why it's better to evaluate the FORM immediately
> after (provide FEATURE) or how that solves Roy's problem of augmenting a
> list-valued variable defvar'ed in the FILE. The advantage of late
Assuming the `provide' is where the coding convention says it should be,
then evaluating FORM right after it means that it's evaluated when the file
has already been fully processed, just as Roy needs it.
And since it relies on the feature name rather than ht efile name, it does
not matter how you decided to load the file.
> I thought it would result in those `defvar's being copied into
> loaddefs.el, which would be dumped into the emacs executable, so they
> could be safely referenced before the "compile" library was actually
> loaded. What am I misunderstanding?
Look at his add-hook code: it intuitively should work. Yet, even with your
suggestion it won't work. Your suggestion allows setting
compilation-error-regexp-alist directly, but it is of no use when the var
is set from the compilation-mode-hook.
Stefan
next prev parent reply other threads:[~2004-02-04 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 16:28 compilation-error-regexp-alist syntax problems Roy Smith
2004-02-02 17:02 ` Stefan Monnier
2004-02-02 21:38 ` Roy Smith
2004-02-03 16:07 ` Stefan Monnier
2004-02-03 17:07 ` Roy Smith
2004-02-03 17:54 ` Stefan Monnier
2004-02-03 19:00 ` Roy Smith
2004-02-03 19:05 ` Kevin Rodgers
2004-02-03 19:31 ` Stefan Monnier
2004-02-03 22:30 ` Kevin Rodgers
2004-02-04 14:50 ` Stefan Monnier [this message]
2004-02-05 19:40 ` Kevin Rodgers
2004-02-05 19:48 ` Stefan Monnier
2004-02-05 8:45 ` Kai Grossjohann
2004-02-05 13:53 ` Roy Smith
2004-02-06 22:03 ` Daniel Pfeiffer
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=jwvy8rizytg.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca \
--to=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.