From: Roger Leigh <rleigh@whinlatter.ukfsn.org>
Subject: Server change broke newsrc.eld
Date: Fri, 21 Jul 2006 11:29:34 +0100 [thread overview]
Message-ID: <slrnec1b4e.5r5.rleigh@hardknott.home.whinlatter.ukfsn.org> (raw)
Hi folks,
(I'm posting this from slrn, having totally broken my gnus setup.)
I run a local leafnode news server, and a few weeks ago I needed to do
some work on it to fix some brokenness in the spool. I ended up needing
to re-create the spool from scratch, and this meant that the article
numbers changed dramatically. The server is working perfectly--I'm
using it with slrn right now.
This caused gnus to behave quite oddly. It now won't view any news, due
to the article numbers being way lower than what is thinks is the
current number.
I have tried removing the offending groups by hand from both ~/.newsrc
and ~/.newsrc.eld. However, on restarting gnus, it still appears to
retain the history for the group (read and marked articles, for
example). Does gnus keep additional history elsewhere?
I also removed the groups from gnus, verified they were no longer
present in .newsrc and .newsrc.eld, and then re-added them (after
restarting gnus), but again the history is still shown in the summary
buffer.
Could anyone possibly suggest how to make gnus "forget" all about the
groups so that I can start from scratch. I also read all my mail with
gnus, so I really don't want to blow away the whole history--just the
news history.
Many thanks,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please sign and encrypt your mail.
next reply other threads:[~2006-07-21 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 10:29 Roger Leigh [this message]
2006-07-21 11:39 ` Lowell Gilbert
2006-07-21 18:17 ` Roger Leigh
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=slrnec1b4e.5r5.rleigh@hardknott.home.whinlatter.ukfsn.org \
--to=rleigh@whinlatter.ukfsn.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).