Gnus development mailing list
 help / color / mirror / Atom feed
From: Rich Pieri <rich.pieri@PrescientTech.com>
Subject: Re: curiosity question
Date: 06 Dec 1996 09:53:57 -0500	[thread overview]
Message-ID: <knhglzvi4a.fsf@gkar.asds.com> (raw)
In-Reply-To: feren@ctron.com's message of 06 Dec 1996 08:11:28 -0500

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "ACF" == Andrew C Feren <feren@ctron.com> writes:

ACF> Other than avoiding clutter are there any other reasons to us a
ACF> .gnus file?

Anything that you would put in .gnus can go in .emacs.  But, do you
really want or need to load all that cruft when you do not need it?  I
do not -- my .gnus (actually .gnus.el because I byte-compile it) is 10K.
Even for those packages that do not have their own separate
customization files I have eval-after-loads for them which load the
separate config files.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Charset: noconv

iQCVAwUBMqgzh56VRH7BJMxHAQFYtwP/TO5zYW4Rskcuq96h8Lkg4Ql4MfEVtqO2
mXnb9C5hQb0aIIdiAFJTCXNHfg71BY2+hZ+5cIT/Fx7RVw7er1gcNaq8GzgZQY0Y
Xyv9b9G2752Gl/SB9I4EaHS+FYcM91JsZ0uo8STrxX4UJ2y28C1FS85YK5020gbp
iv+1ZC2VRM4=
=rhKC
-----END PGP SIGNATURE-----
-- 
Rich Pieri <rich.pieri@prescienttech.com> | Always give generously - a small
      Prescient Technologies, Inc.        | bird or rodent left on the bed
       A Stone & Webster Company          | tells them, "I care".
  I speak for myself, not PTI or SWEC     | --A cat's guide to life


      parent reply	other threads:[~1996-12-06 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-12-06 13:11 Andrew C. Feren
1996-11-17 15:44 ` William Perry
1996-12-06 21:56   ` Daniel Simms
1996-12-06 13:32 ` Lars Magne Ingebrigtsen
1996-12-09 14:44   ` Andrew C. Feren
1996-12-06 14:13 ` Lars Balker Rasmussen
1996-12-06 14:53 ` Rich Pieri [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=knhglzvi4a.fsf@gkar.asds.com \
    --to=rich.pieri@prescienttech.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).