From: akb+lists.ding@mirror.to (Andrew B)
To: ding@gnus.org
Subject: Re: help with corrupted files; ticked articles missing
Date: Thu, 03 Aug 2023 18:21:50 -0400 [thread overview]
Message-ID: <0qleer3gxt.fsf@mirror.to> (raw)
In-Reply-To: <86jzv2npjr.fsf@simplex.rtf.org.uk> (RL's message of "Fri, 14 Jul 2023 22:36:40 +0100")
RL <richard.lewis.debian@googlemail.com> writes:
> akb+lists.ding@mirror.to (Andrew B) writes:
>
>> The partition containing my home directory filled up, and I cleared
>
>> What can I do to recover my unread and ticked articles?
>> Are there any files besides .newsrc ones that I need to recover gnus
>> state?
>
> I had a similar situation - i found the 'active' file in the nnml server
> had been emptied and this seems to have caused issues opening nnml
> groups. Running `M-x nnml-generate-nov-databases' seems to have fixed it,
> but i dont know if this is good or bad advice
Thanks! This put me on the right track. I don't use nnml, but there
were files in the ~/News directory causing the problem; if I have time
I'll sort out what exactly, but meanwhile I just renamed the direcoty
contents and let gnus recreate what it needed.
Meanwhile, if there's a wishlist, I feel like this sort of thing should
not ideally be possible; with nnimap if M-g shows me there are
1000 ticked articles and entering the group only shows 1, or if M-g
shows 124000 articles, but entering the group refuses to retrieve more
than a couple dozen, I feel like there could be some kind of internal
consistency check that at least informs the user that there's a problem,
and ideally allows for something like overwriting corrupt info in
either .newsrc.eld or ~/News with info from the imap server...
prev parent reply other threads:[~2023-08-03 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 10:13 Andrew B
2023-07-03 4:08 ` Eric Abrahamsen
2023-07-13 19:44 ` Andrew B
2023-07-14 21:36 ` RL
2023-08-03 22:21 ` Andrew B [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=0qleer3gxt.fsf@mirror.to \
--to=akb+lists.ding@mirror.to \
--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).