unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: emacs-devel@gnu.org
Subject: Re: custom problem
Date: Tue, 31 Dec 2002 15:29:26 +0100	[thread overview]
Message-ID: <rjof72p8hl.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: <200212302251.gBUMp8G10002@arc.math.ohio-state.edu> (Markus Rost's message of "Mon, 30 Dec 2002 17:51:08 -0500 (EST)")

[ CC'ed to emacs-devel ]

Markus Rost <rost@math.ohio-state.edu> writes:

> Yes.  This was meant for prompts for customize-variable,
> customize-group and friends, also for describe-variable, which should
> give a hint that the variable can be customized.  You don't want to
> load libraries here in advance.

I don't think it is a problem to load a file if you are trying to get
information (or customize) a *specific* variable (or face or group)
defined in that file.

However, it could be a problem if we load files as a result of a more
generic search, like the apropos commands, creating a customize menu,
or a customize buffer for a group containing variables from many
unrelated files, like the "basic customization" group suggested on
emacs-devel. 

> However, meanwhile I think that one should not change the format of
> the custom-loads property.  The current format of custom-loads is
> pretty simple and handy, and other packages may rely on it.

I doubt any unbundled code depend on on the custom-loads property.

       reply	other threads:[~2002-12-31 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E18R1Z9-0000Zz-00@fencepost.gnu.org>
     [not found] ` <200212251025.gBPAPeJ14720@arc.math.ohio-state.edu>
     [not found]   ` <rjof73xt0t.fsf@zuse.dina.kvl.dk>
     [not found]     ` <200212302251.gBUMp8G10002@arc.math.ohio-state.edu>
2002-12-31 14:29       ` Per Abrahamsen [this message]
2003-01-02 13:05         ` custom problem Per Abrahamsen

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=rjof72p8hl.fsf@zuse.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    --cc=emacs-devel@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).