Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: What value .gnus?
Date: Fri, 06 Sep 2002 15:21:19 +0200	[thread overview]
Message-ID: <vaffzwnb6eo.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <873csn1fip.fsf@smtp.blueyonder.co.uk>

Keith O'Connell <keith_oconnell@blueyonder.co.uk> writes:

> When I use the emacs customisation options to modify it, the changes
> are put into .emacs, even the changes specific to gnus are put in
> .emacs. This being the case, what is the value of a .gnus file? Why
> maintain two if the program itself tends to create just the one.

Some people prefer to keep the settings separate.  Other people
prefer a single file.

Sadly, Customize doesn't give you a choice, but oh, well.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)


       reply	other threads:[~2002-09-06 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873csn1fip.fsf@smtp.blueyonder.co.uk>
2002-09-06 13:21 ` Kai Großjohann [this message]
2002-09-06 19:43 ` Henrik Enberg

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=vaffzwnb6eo.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).