From: Mark Borges <mdb@cdc.noaa.gov>
Subject: Re: [Gnus-5.5] Changing news server -- how well does it work?
Date: 27 Apr 1998 15:09:09 -0600 [thread overview]
Message-ID: <vkvhrvhszu.fsf@cdc.noaa.gov> (raw)
In-Reply-To: Mark Borges's message of "23 Apr 1998 12:23:01 -0600"
>> On 23 Apr 1998 12:23:01 -0600,
>> Mark Borges(mb) wrote:
mb> My current newsfeed (news.colorado.edu) has become extremely flaky,
mb> and I would like to move to an alternate as my primary server. I've
mb> read through the `Changing Servers' node on the info pages, and am
mb> very tempted to switch servers using gnus-change-server().
mb> Does this work reasonably well, or will I find some unexpected and/or
mb> undocumented surprises? In particular, I'm curious how the transition
mb> will handle:
mb> (1) cached news articles. I have saved many old articles to local
mb> disk, and wonder if I'll continue to have access to them (with
mb> their old article numbers) via the Gnus interface.
Now that I've switched (and hand-edited the .eld file to preserve my
mailfolder ticks) I've run into a problem -- it seems that some of the
articles in my cache folder have article numbers larger than those for
the same group in the new server. Consequently, I think this is
confusing Gnus such that the *Group* buffer never shows any new
articles as arriving (when in fact there are).
Is there a simple way to resequence one's cached article numbers to
start at a lower number?
I tried using gnus-cache-generate-active(), but you don't want to know
how much fun that was to recover from (somehow my top level
~/Mail/active file got wiped out). So, before I try shoot myself in
the foot again, I thought I'd ask if others have run into this
problem, and, if so, what the solution was.
Thanks.
--
-mb-
next prev parent reply other threads:[~1998-04-27 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-23 18:23 Mark Borges
1998-04-23 19:24 ` Dan Christensen
1998-04-27 21:09 ` Mark Borges [this message]
1998-04-28 1:48 ` 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=vkvhrvhszu.fsf@cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
/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).