unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: doc problems with defcustom
Date: Tue, 08 Jun 2004 15:52:20 +0900	[thread overview]
Message-ID: <buo65a2pmmz.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20040608.073002.238272728.wl@gnu.org> (Werner LEMBERG's message of "Tue, 08 Jun 2004 07:30:02 +0200 (CEST)")

Werner LEMBERG <wl@gnu.org> writes:
> Neither in emacs.info nor elisp.info it is described how to customize
> a variable defined with defcustom in a non-interactive way, this is,
> how to configure it the `.emacs' file instead of using the `customize'
> feature

Perhaps that's because it's the same as it has always been -- just use
setq, or add-to-list, or whatever you like.
Werner LEMBERG <wl@gnu.org> writes:

> For me, the easiest way is to write
>
>   (add-to-list 'reftex-include-file-commands "CJKinclude")
>
> in `.emacs' (and this is what I recommend my users).

That should be fine.

Actually for lists, customize's behavior is kind of non-optimal anyway,
because one can't just _add_ to a list with customize, you have to
explicitly set the whole thing, which can interact badly with upgrades
&c.

Personally I use a mixture of explicit .emacs settings and customize,
whatever is most convenient for the task at hand (for complicated data
structures, customize can be nice because it often provides little
mini-editors for the data structure).

-Miles
-- 
"Though they may have different meanings, the cries of 'Yeeeee-haw!' and
 'Allahu akbar!' are, in spirit, not actually all that different."

  reply	other threads:[~2004-06-08  6:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08  5:30 doc problems with defcustom Werner LEMBERG
2004-06-08  6:52 ` Miles Bader [this message]
2004-06-08  6:58   ` Werner LEMBERG
2004-06-08  7:59     ` Kim F. Storm
2004-06-08  8:25       ` Juanma Barranquero
2004-06-08  9:23         ` Miles Bader
2004-06-08  9:33           ` David Kastrup
2004-06-08  9:35         ` Per Abrahamsen
2004-06-08 11:02         ` Kenichi Handa
2004-06-08 10:20       ` Kenichi Handa
2004-06-08 10:49         ` Stephan Stahl
2004-06-09  1:15         ` Miles Bader
2004-06-08 23:31       ` Richard Stallman
2004-06-08 23:31     ` Richard Stallman
2004-06-09  5:18       ` Werner LEMBERG
2004-06-10  6:55         ` Richard Stallman

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=buo65a2pmmz.fsf@mctpc71.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).