From: Tassilo Horn <tassilo@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: reading compile.el, modifying settings
Date: Thu, 05 May 2011 12:44:04 +0200 [thread overview]
Message-ID: <87wri5jukr.fsf@member.fsf.org> (raw)
In-Reply-To: 1933055643.48627.1304431423078.JavaMail.root@aksu.oays-ds.com
Paul Graham <pgraham@oasys-ds.com> writes:
Hi Paul,
> I use compile mode, but I have my own set of compiler
> message regexps. I try to set them up as follows:
>
> .emacs:
>
> (load "compile")
> (load-file "~/emacs/compile-settings.el")
>
> compile-settings.el:
>
> (setq compilation-error-regexp-alist ... )
That looks good, except one would normally do (require 'compile), but
that shouldn't be any different here.
> However, when I compile in emacs, I end up with the
> default compiler message regexps. I then have to
> manually eval the load of compile-settings.el to
> get my settings.
>
> I think that when emacs starts up, it picks up my
> setting for compilation-error-regexp-alist, but does
> not immediately load compile.elc. Then when I do my
> first compile, it loads compile.elc, and overwrites
> my settings.
No, `load' shouldn't defer loading. And even if it did, it should do no
harm, because `compilation-error-regexp-alist' is a defcustom and like
for defvars, the default value is only set if the variable is not
already bound.
Hm, maybe you should check if there is some other compile.el on your
load-path which gets loaded instead of the "real emacs" compile.el.
(M-x list-load-path-shadows RET).
Bye,
Tassilo
next prev parent reply other threads:[~2011-05-05 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:03 reading compile.el, modifying settings Paul Graham
2011-05-05 10:44 ` Tassilo Horn [this message]
2011-05-12 12:49 ` Oleksandr Gavenko
2011-05-05 16:31 ` Sam Steingold
2011-05-05 18:15 ` Tassilo Horn
2011-05-05 18:34 ` Sam Steingold
2011-05-05 19:09 ` Tassilo Horn
2011-05-05 21:08 ` Sam Steingold
2011-05-06 7:13 ` Tassilo Horn
2011-05-05 19:48 ` Tassilo Horn
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=87wri5jukr.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=help-gnu-emacs@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 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.