From: Drew Adams <drew.adams@oracle.com>
To: tomas@tuxteam.de, help-gnu-emacs@gnu.org
Subject: RE: which one to use: custom-set-variables, customize-set-variable, or customize-set-value?
Date: Sun, 13 Dec 2015 09:32:14 -0800 (PST) [thread overview]
Message-ID: <1bb3e90b-9e31-4450-aa11-4c475ffd081a@default> (raw)
In-Reply-To: <20151213081701.GA25363@tuxteam.de>
> > As I said, you can certainly do as you suggest. My suggestion is
> > to clearly show in your init file how you are setting the value.
> > Including for different Emacs versions - so you are aware of such
> > changes when you read your code later. But it's just a suggestion.
>
> Here I was trying to make a case for some kind of "generic setter"
> which knows what the right thing is. Of course, such a generic setter
> wouldn't be half as valuable without a context. I wouldn't do it in
> my init file as of now, where it's not "usual".
BTW, maybe I should also have made clear that I think the best
practice, in general, is to use the Customize UI and let it
manage user options and faces, and to force it to do so in a
separate `custom-file' and not in the init file.
While one can call Customize functions (`customize-set-variable')
from Lisp code, my advice is to save that for commands you write
that dynamically manipulate (set and possibly save) options and
faces - as opposed to using such functions in an init file.
(Just one opinion.)
next prev parent reply other threads:[~2015-12-13 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 18:47 which one to use: custom-set-variables, customize-set-variable, or customize-set-value? Alan Schmitt
2015-11-29 19:19 ` Drew Adams
2015-11-30 8:52 ` Alan Schmitt
2015-11-30 15:20 ` Drew Adams
2015-11-30 15:44 ` Alan Schmitt
2015-12-11 18:23 ` Lele Gaifax
2015-12-11 18:53 ` Drew Adams
2015-12-12 8:31 ` Lele Gaifax
2015-12-12 12:09 ` tomas
2015-12-12 13:31 ` Lele Gaifax
2015-12-12 16:11 ` Drew Adams
2015-12-13 8:17 ` tomas
2015-12-13 17:32 ` Drew Adams [this message]
2015-12-14 2:44 ` B.V. Raghav
2015-12-14 8:28 ` Lele Gaifax
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=1bb3e90b-9e31-4450-aa11-4c475ffd081a@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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).