Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: new feature request
Date: 21 Dec 1999 21:56:30 +0100	[thread overview]
Message-ID: <vafln6o57y9.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Laura Conrad's message of "16 Dec 1999 13:33:33 -0500"

I think that's a good idea.  I think Gnus should move from the
monolithic .newsrc.eld to a number of files.  Maybe a ~/.newsrc-gnus/
directory would be nice with a number of files in it, named after the
backend?  Superfluous files could be ignored, and Bob would be your
uncle.

Sounds like doable work (though saving info in the right file might be
difficult), if rather tedious.

kai
-- 
A preposition is not a good thing to end a sentence with.



  parent reply	other threads:[~1999-12-21 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16 18:33 Laura Conrad
1999-12-20  2:02 ` Brian May
1999-12-20 16:30   ` Alex Schroeder
1999-12-20 22:38 ` Brian May
1999-12-21 20:56 ` Kai Großjohann [this message]
2000-04-21 17:49   ` Lars Magne Ingebrigtsen

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