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 20:15:29 +0200 [thread overview]
Message-ID: <87zkn1ui7y.fsf@member.fsf.org> (raw)
In-Reply-To: svpqnxxg6n.fsf@tbox.wtc.algo
Sam Steingold <sds@gnu.org> writes:
Hi Sam,
>> (setq compilation-error-regexp-alist ... )
>
> compilation-error-regexp-alist is defined with defcustom, so it should
> be modified with custom-set-variables, not with setq. Don't ask.
No, that's not true. You can setq any defcustom as if it was a defvar.
The former is only some macro that eventually expands to a defvar, but
contains some more metadata for the customize interface.
Bye,
Tassilo
next prev parent reply other threads:[~2011-05-05 18:15 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
2011-05-12 12:49 ` Oleksandr Gavenko
2011-05-05 16:31 ` Sam Steingold
2011-05-05 18:15 ` Tassilo Horn [this message]
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
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=87zkn1ui7y.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.
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).