Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Wizards (was: Re: Oort Version)
Date: 28 Mar 2001 11:34:42 -0500	[thread overview]
Message-ID: <m366gtc0nb.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vxksnjyc5n3.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "28 Mar 2001 09:47:12 -0500")

Karl Kleinpaste <karl@charcoal.com> writes:
> The advantage of .gnus is that it is loaded with every start of Gnus.
> If we bury customizations in the usual auto-customize file, fresh
> invocations of Gnus in a new Emacs don't get needed stuff picked up,
> and induce another nightmare for the confused new user.

But will new users often be in that situation?  Maybe have a variable
gnus-custom-file, which could be either "~/.gnus-custom" or
'custom-file by default.  Store Gnus custom stuff in there.


paul


  parent reply	other threads:[~2001-03-28 16:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 19:00 Oort Version Jake Colman
2001-03-26 20:05 ` Kai Großjohann
2001-03-26 20:29   ` Karl Kleinpaste
2001-03-27 21:02     ` Simon Josefsson
2001-03-27 21:33       ` Steven E. Harris
2001-03-27 22:29         ` Robin S. Socha
2001-03-28  0:13           ` Karl Kleinpaste
2001-03-28  0:38             ` Colin Marquardt
2001-03-28 18:06               ` Josh Huber
2001-03-28  3:40             ` Simon Josefsson
2001-03-28 18:51               ` Samuel Padgett
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:15             ` Christoph Conrad
2001-03-28  7:21             ` Christoph Conrad
2001-03-28  8:43               ` Christoph Conrad
2001-03-28 13:59             ` Wizards (was: Re: Oort Version) Per Abrahamsen
2001-03-28 14:47               ` Karl Kleinpaste
2001-03-28 15:58                 ` Per Abrahamsen
2001-03-28 16:34                 ` Paul Jarc [this message]
2001-03-28 22:38                 ` Alex Schroeder
2001-03-28 19:03               ` Samuel Padgett

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=m366gtc0nb.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).