From: Laura Conrad <lconrad@gamesville.com>
Subject: new feature request
Date: 16 Dec 1999 13:33:33 -0500 [thread overview]
Message-ID: <kh74sdizqf6.fsf@acme47.nineco.com> (raw)
While we're discussing potential new features for the next version:
What about figuring out a way so that changing the primary server
doesn't destroy information about groups that come from a secondary
server? Or better yet, get rid of the idea of a primary server
altogether. Just have a bunch of equal servers that store information
about their articles independantly.
If I've stated this at the wrong level of abstraction, here's a
different level: Right now, the näive user (for this purpose,
including me) who changes newsservers not only loses all the
information contained in the marks in the nntp groups, which you would
expect, and which is documented in the manual, he or she also
loses this information in the nnml groups. This is annoying.
Yes I know that if you're careful about what you name the .newsrc*
files you can probably change your nntp newsserver and still keep all
the marks on your nnml groups, but I can't say I've ever managed to do
it. Even if I did manage it with the help of all the high-powered
gnus experts on this list, that still wouldn't prove that the
gnus-user-on-the-street could do it.
I have gotten much faster than I used to be at restoring the correct
marks on my mail groups when I do clobber them...
--
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next reply other threads:[~1999-12-16 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-16 18:33 Laura Conrad [this message]
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
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=kh74sdizqf6.fsf@acme47.nineco.com \
--to=lconrad@gamesville.com \
--cc=lconrad@world.std.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).