From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: new feature request
Date: 20 Dec 1999 13:02:13 +1100 [thread overview]
Message-ID: <t4iln6qjroa.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Laura Conrad's message of "Thu, 16 Dec 1999 13:33:33 -0500"
>>>>> "Laura" == Laura Conrad <lconrad@gamesville.com> writes:
Laura> Yes I know that if you're careful about what you name the
Laura> .newsrc* files you can probably change your nntp newsserver
Laura> and still keep all the marks on your nnml groups, but I
Laura> can't say I've ever managed to do it. Even if I did manage
Laura> it with the help of all the high-powered gnus experts on
Laura> this list, that still wouldn't prove that the
Laura> gnus-user-on-the-street could do it.
There is, I think, an automatic way of translating the .newsrc* files
to a new server. It is documented in the Info documentation. I have
never used myself.
I don't think there is any automatic way of keeping cached
articles.... IIRC, the info documentation says that these must be
deleted in order to prevent confusion.
The only way to keep track of a message independently of the server,
is to use its message id, rather then its message number. Perhaps a
new backend could be designed, that saves messages by id, rather then
number. However, I doubt it would be this easy, as I suspect most of
Gnus refers to messages by number. Or perhaps it might be possible to
have some virtual numbering scheme independent of the server. I don't
know. These are just some issues you might want to think about.
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-20 2:02 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 [this message]
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=t4iln6qjroa.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).