Gnus development mailing list
 help / color / mirror / Atom feed
From: Sam Falkner <samf@central.sun.com>
Subject: breaking up .newsrc.eld (was Re: Oort Gnus)
Date: 19 Jan 2000 10:25:26 -0700	[thread overview]
Message-ID: <ii7901m0y9l.fsf_-_@central.sun.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "18 Jan 2000 14:20:27 +0100"

I would like it if .newsrc.eld were broken up into "configuration" and
"current state (aka .newsrc)".  I'd like this because configuration
stuff is appropriate for moving between sites, but current state is
site-specific.

I keep most of my config files between work and home "in sync".
Changes I make to my .emacs at work will soon end up at home, and
vice-versa.  (I do this via the perforce source control package, and
it's very nice, if you care. :-)

But for gnus, .emacs and .gnus don't quite cover it.  Much of the data
that I care about is in the .newsrc.eld file.  Stuff like the group
and topic hierarchy, and group and topic parameters.  I can't copy
.newsrc.eld back and forth between work and home, because I don't have
the same articles and NNTP servers available in both places.

I think I could partially work around the problem by copying
.newsrc.eld and touching the local .newsrc so that it was newer.  But
that wouldn't work for email, and email is very important to me.

I'm not sure of the best way to do this.  Create a new config file,
mostly maintained by gnus (like a score or adapt file, or an active
file), and have .newsrc.eld become nothing more than a .newsrc that's
made into S-expressions would be my first thought.

- Sam



  parent reply	other threads:[~2000-01-19 17:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-17  0:55 Oort Gnus Lars Magne Ingebrigtsen
2000-01-17 20:02 ` Alexandre Oliva
2000-01-17 23:31   ` Denys Duchier
2000-01-18  2:08     ` Eric S. Johansson
2000-01-18  3:59       ` Johan Kullstam
2000-01-18 13:20         ` Kai Großjohann
2000-01-18 13:31           ` Harry Putnam
2000-01-18 20:43             ` Steinar Bang
2000-01-20 13:40             ` Big Gaute
2000-01-18 14:27           ` Raymond Scholz
2000-01-18 16:35           ` Randal L. Schwartz
2000-01-18 20:16             ` Colin Rafferty
2000-01-19  0:12           ` David Hedbor
2000-01-19  1:05           ` Daniel Pittman
2000-01-19 17:25           ` Sam Falkner [this message]
2000-01-19 17:37             ` breaking up .newsrc.eld (was Re: Oort Gnus) lconrad
2000-01-19 17:53               ` Steve Harris
2000-01-19 17:49             ` Steve Harris
2000-01-19 20:50             ` Kai Großjohann
2000-01-20 11:43               ` breaking up .newsrc.eld Toby Speight
2000-01-20 12:21                 ` Kai Großjohann
2000-01-20 12:24                   ` Kai Großjohann
2000-01-29 16:41           ` Oort Gnus Matt Simmons
2000-01-29 17:06             ` Alan Shutko
2000-01-30  2:20               ` Oyvind Moll
2000-01-30 15:18                 ` Colin Rafferty
2000-01-30 15:44                   ` Fabrice Popineau
2000-02-01  6:57               ` Jaap-Henk Hoepman
2000-01-31 16:42             ` Per Abrahamsen
2000-01-17 20:47 ` Steinar Bang
2000-01-18 15:50   ` Mick Gower
2000-01-19 15:31     ` Jerry James

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=ii7901m0y9l.fsf_-_@central.sun.com \
    --to=samf@central.sun.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).