From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: customize question
Date: Fri, 20 Dec 2002 20:22:40 +0100 [thread overview]
Message-ID: <84of7g7awv.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: 86d6nwk9oy.fsf@kronstadt.homeunix.net
Ian Zimmerman <itz@speakeasy.org> writes:
> I'd like to reuse a customized variable (which is not autoloaded) from
> another package in my code. Is there a way to do that other than
> (require 'otherpackage) ?
You could autoload it.
> (In particular, I was thinking of declaring the same variable myself,
> either in my group or in the group of the other package. What would
> be the effect of that, and can it be depended on?)
Oh, no. Better don't do that. I think it's not a good idea to change
the custom spec of a variable. And if you do, load order determines
who wins.
How about just requiring the package and adding the variable to your
own custom group? I believe that defgroup allows you to list some
variables which are to be in that group.
--
~/.signature is: umop ap!sdn (Frank Nobis)
prev parent reply other threads:[~2002-12-20 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 15:10 customize question Ian Zimmerman
2002-12-20 17:50 ` Kevin Rodgers
2002-12-20 19:22 ` Kai Großjohann [this message]
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=84of7g7awv.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.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).