Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus fucks up my custom settings
Date: 05 Mar 1999 21:22:19 +0100	[thread overview]
Message-ID: <m3aexrg004.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Colin Rafferty's message of "05 Mar 1999 09:57:04 -0500"

Colin Rafferty <craffert@ms.com> writes:

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

It makes sense in one way, but in other ways it doesn't.  For
instance, putting variables in one whopping big file means that they
aren't local to the functionality being provided.  So even if you
don't plan on using picons, you'll get a gazillion picons-related
variables defined when you start Gnus.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1999-03-05 20:22 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
1999-03-05 20:22   ` Lars Magne Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3aexrg004.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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 NNTP newsgroup(s).