From: Sam Steingold <sds@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: reading compile.el, modifying settings
Date: Thu, 05 May 2011 14:34:11 -0400 [thread overview]
Message-ID: <svfwotxaho.fsf@tbox.wtc.algo> (raw)
In-Reply-To: 87zkn1ui7y.fsf@member.fsf.org
Hi Tassilo,
> * Tassilo Horn <gnffvyb@zrzore.sfs.bet> [2011-05-05 20:15:29 +0200]:
> Sam Steingold <sds@gnu.org> writes:
>>
>> 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.
Sure. You can setq any symbol.
However, the _effect_ of setq on a variable defined with defcustom is
different - it is not respected by emacs on the same level as
custom-set-variables.
At least it was not a few years ago, when I had the same problem - my
setting being ignored - as Paul is having now.
1. some packages use symbol properties in addition to the symbol value,
these are modified by custom-set-variables automatically
2. some custom variables have fancy setters which are called by
custom-set-variables but not by setq (like symbol macros in CL)
In short, the rule of thumb is: do not use setq on custom variables, use
custom-set-variables instead.
--
Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031
http://honestreporting.com http://camera.org http://palestinefacts.org
http://ffii.org http://www.PetitionOnline.com/tap12009/ http://truepeace.org
"Syntactic sugar causes cancer of the semicolon." -Alan Perlis
next prev parent reply other threads:[~2011-05-05 18:34 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
2011-05-05 18:34 ` Sam Steingold [this message]
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=svfwotxaho.fsf@tbox.wtc.algo \
--to=sds@gnu.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).