From: Tassilo Horn <tassilo@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: reading compile.el, modifying settings
Date: Fri, 06 May 2011 09:13:44 +0200 [thread overview]
Message-ID: <87bozgjo7r.fsf@member.fsf.org> (raw)
In-Reply-To: sv39ksyhxr.fsf@tbox.wtc.algo
Sam Steingold <sds@gnu.org> writes:
Hi Sam,
>> ,----
>> | ;; foo is not defined before
>> | (setq foo 17)
>> | ;; now load its defcustom
>> | (defcustom foo 111
>> | "Bla bla")
>> | ;; still has my value plus the props of the defcustom
>> | (cons foo (symbol-plist 'foo))
>> | ==> (17 standard-value (111) custom-requests nil variable-documentation
>> | "Bla bla")
>> `----
>
> that's my point - a custom variable is much more than just a
> symbol-value.
Yes, and my point is that setq does no harm either.
> I wonder, however, if my solution solves Paul's problem.
Ditto.
>> My emacs is highly customized in plain lisp only, so that I can
>> comment what I do and structure it according to my likings.
>
> Mine too - and I use custom-set-variables for all custom vars in
> ~/.emacs. And, of course, both setq and custom-set-variables are
> "plain lisp".
Sure, with plain list I've meant any lisp not beginning with
custom-*. ;-)
But assuming you are right, why don't the docs state anything about that
users should use `custom-set-variables'? And why is there no `setc'
macro for users preferring customization in lisp for setting variables,
which expands to a `custom-set-variables' form for defcustoms?
(info "(emacs)Init Examples") setqs custom variables quite happily...
Bye,
Tassilo
next prev parent reply other threads:[~2011-05-06 7:13 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
2011-05-05 19:09 ` Tassilo Horn
2011-05-05 21:08 ` Sam Steingold
2011-05-06 7:13 ` Tassilo Horn [this message]
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=87bozgjo7r.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).