From: Colin Rafferty <craffert@ms.com>
Subject: Re: Gnus fucks up my custom settings
Date: 05 Mar 1999 09:57:04 -0500 [thread overview]
Message-ID: <vgvaexs2ddr.fsf@ms.com> (raw)
In-Reply-To: Didier Verna's message of "05 Mar 1999 10:15:33 +0100"
Didier Verna writes:
> I see 2 solutions to this problem: either you require each library
> from which you'll twiddle a variable (but then you might load libs that the
> user wo't use), or you use defcustom instead of defvar (but then you have code
> replication). Or maybe the concerned variables should be defined in a separate
> file instead of in their respective libs ?
I vote for your third solution.
This seems to be the simplest way to deal with large packages with
lots of variables, all of which need to be customized.
vm, cc-mode, and w3 all do it this way, and it makes sense.
--
Colin
next prev parent reply other threads:[~1999-03-05 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 9:15 Didier Verna
1999-03-05 14:57 ` Colin Rafferty [this message]
1999-03-05 20:22 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vgvaexs2ddr.fsf@ms.com \
--to=craffert@ms.com \
/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 NNTP newsgroup(s).