From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: curiosity question
Date: 06 Dec 1996 14:32:20 +0100 [thread overview]
Message-ID: <m220d36bob.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: feren@ctron.com's message of 06 Dec 1996 08:11:28 -0500
feren@ctron.com (Andrew C. Feren) writes:
> Other than avoiding clutter are there any other reasons to us a .gnus
> file?
Well, the .gnus.el file is read each time you start Gnus, which can be
good or bad. Also, many of the Gnus variables are defined when
.gnus.el is evaled, which can be a plus. Or not.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1996-12-06 13:32 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 [this message]
1996-12-09 14:44 ` Andrew C. Feren
1996-12-06 14:13 ` Lars Balker Rasmussen
1996-12-06 14:53 ` Rich Pieri
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=m220d36bob.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).