Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
Cc: ding@gnus.org
Subject: Re: cache shadows postings after article number reset
Date: Sat, 26 Feb 2005 03:26:29 +0100	[thread overview]
Message-ID: <m3wtswjbu2.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <uzmxsfe93.fsf@vignette.com> (Kevin Greiner's message of "Fri, 25 Feb 2005 16:47:52 -0600")

Kevin Greiner <kevin.greiner@vignette.com> writes:

> Matthias Andree <matthias.andree@gmx.de> writes:
>
>> Hi,
>>
>> one of my newsservers recently reset article numbers. For a particular
>> group, the numbers are in the 500,000-510,000 range, but from the "old
>> times", I have an article in the 800,000 range in the cache for that
>> group. Any new articles arriving with a lower number aren't shown by
>> Gnus.
>>
>> Are there any settings I can change to overcome this? Or can I just
>> "move down" article numbers in the cache? Do I need to regenerate
>> indexes or something after renaming for instance 876,543 to 12,345?
>
> A couple of options exist.
>
> The easiest is to simply delete the agent directory for the group.
> You'll loose all of your off-line content.

Not agentised, but articles cached (saved, archived) with the [*] key.

> The next harder is to open the agent directory.  Delete the file named
> .overview then rename each article file to its new number.  When
> you're done, go to the summary buffer, position point on the group in
> question then enter M-x gnus-agent-regenerate-group<ret>.  This will
> preserve your off-line articles but you have to fetch the active
> headers.

Will consider that next time. Thanks.

-- 
Matthias Andree



      reply	other threads:[~2005-02-26  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 23:52 Matthias Andree
2005-02-24 16:27 ` Reiner Steib
2005-02-25  0:02   ` Matthias Andree
2005-02-25 22:47 ` Kevin Greiner
2005-02-26  2:26   ` Matthias Andree [this message]

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=m3wtswjbu2.fsf@merlin.emma.line.org \
    --to=matthias.andree@gmx.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).