From: "Drew Adams" <drew.adams@oracle.com>
To: "'David Combs'" <dkcombs@panix.com>, <help-gnu-emacs@gnu.org>
Subject: RE: re-loading an elisp file
Date: Thu, 24 Mar 2011 12:09:19 -0700 [thread overview]
Message-ID: <13CE6AB41DE34088955029C4B450CBA8@us.oracle.com> (raw)
In-Reply-To: <img28k$n3i$2@reader1.panix.com>
> > And even in user init files, practice over the years has
> > tended to reduce the habit of using setq in favor of
> > taking advantage of Customize (defcustom). There are
> > several reasons for that, including type-checking
> > and initialization with side effects (i.e., initializing a
> > variable can also call for other, related initialization
> > operations).
>
> Customize -- hmmm -- interesting (though I've never used it,
> always preferred edit-options kind of thing).
>
> But please say more about your suggested use of customize in this
> situation. Thanks!
Dunno what "this situation" is. And I don't have a suggested use of customize.
I use `defcustom' to define variables that I expect general users to want to
modify. That makes the variables into user options, which means their values
can be changed using `M-x set-variable' or `M-x customize-option'.
> Also, some more about its type checking, and its initialization
> with side-effects.
See the `defcustom' doc wrt :type, :init, and :set.
(elisp) Variable Definitions
(elisp) Customization Types
> Maybe also some examples of how you use it in your code-writing.
Check the Lisp sources that come with Emacs. Grep `:type' or `:set' or
`:initialize'.
next prev parent reply other threads:[~2011-03-24 19:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 15:16 re-loading an elisp file ken
2011-03-05 15:54 ` Drew Adams
2011-03-05 17:13 ` ken
2011-03-05 18:06 ` Drew Adams
2011-03-05 18:11 ` Drew Adams
2011-03-05 23:36 ` ken
2011-03-06 2:08 ` PJ Weisberg
[not found] ` <mailman.22.1299377327.22865.help-gnu-emacs@gnu.org>
2011-03-24 18:31 ` David Combs
2011-03-24 18:57 ` Drew Adams
[not found] ` <mailman.4.1299348453.24947.help-gnu-emacs@gnu.org>
2011-03-24 18:24 ` David Combs
2011-03-24 19:09 ` Drew Adams [this message]
[not found] ` <mailman.0.1299345251.24947.help-gnu-emacs@gnu.org>
2011-03-05 22:25 ` Tim X
[not found] <mailman.6.1299338195.13665.help-gnu-emacs@gnu.org>
2011-03-05 15:27 ` Pascal J. Bourguignon
2011-03-05 16:46 ` ken
[not found] ` <mailman.18.1299343589.13665.help-gnu-emacs@gnu.org>
2011-03-05 17:41 ` Johan Bockgård
2011-03-05 23:09 ` ken
2011-03-05 22:17 ` Tim X
2011-03-05 23:21 ` PJ Weisberg
[not found] ` <mailman.3.1299367324.22865.help-gnu-emacs@gnu.org>
2011-03-06 0:05 ` Tim X
2011-03-06 5:32 ` rusi
2011-03-06 8:36 ` Le Wang
2011-03-08 1:18 ` Kevin Rodgers
[not found] ` <mailman.0.1299547100.4111.help-gnu-emacs@gnu.org>
2011-03-08 1:57 ` rusi
2011-03-08 2:01 ` rusi
2011-03-24 18:02 ` David Combs
2011-03-25 6:39 ` Tim X
2011-03-25 6:51 ` David Kastrup
2011-03-25 8:45 ` Jambunathan K
2011-03-25 22:23 ` Tim X
[not found] ` <mailman.2.1301064125.24725.help-gnu-emacs@gnu.org>
2011-03-25 23:01 ` Tim X
2011-03-26 4:25 ` Jambunathan K
[not found] ` <mailman.0.1301164236.2084.help-gnu-emacs@gnu.org>
2011-03-26 22:49 ` Tim X
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=13CE6AB41DE34088955029C4B450CBA8@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=dkcombs@panix.com \
--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).