From: Shenghuo ZHU <zsh@cs.rochester.edu>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: Peculiar treatment of edited messages
Date: 25 Oct 1999 12:45:29 -0400 [thread overview]
Message-ID: <5bpuy3v17a.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Ted Stern's message of "25 Oct 1999 08:48:59 -0700"
>>>>> "Ted" == Ted Stern <stern@tera.com> writes:
>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
[...]
ZSH> To bring back those missing articles, I tried to move all
ZSH> articles in the group to a temporary group, then rescan the
ZSH> group, and repeat
Ted> ^^^^^^^^^^^^^^^^
Ted> ??? will this work even if the previously edited files no longer show
Ted> in the summary buffer?
[...]
In Gnus, there are some codes to rebuild the nnfolder-article-marker.
I am not sure when they are executed. Here are some comments. When you
move all articles with marker from the group, the articles without
marker tends to be at the end of the file (folder). Then the codes are
executed.
,--------
| ;; As long as we trust that the user will only insert unmarked mail
| ;; at the end, go to the end and search backwards for the last
| ;; marker. Find the start of that message, and begin to search for
| ;; unmarked messages from there.
`--------
BTW, it seems to need some codes (nnoo-request-check-consistence) to
automatically check and fix the consistence of back-ends, just like
fsck does on file-systems. We often got problems like expiration
problem (some expirable articles are never removed. similar problem in
agent), consistence in cache, missing articles, bad overview or active
files, unwanted directories. Any more?
--
Shenghuo
next prev parent reply other threads:[~1999-10-25 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-19 18:16 Ted Stern
1999-10-20 2:24 ` Dan Christensen
1999-10-24 18:29 ` Dan Christensen
1999-10-24 19:53 ` Shenghuo ZHU
[not found] ` <yccbt9nmoes.fsf@orff.sea.tera.com>
1999-10-25 16:45 ` Shenghuo ZHU [this message]
1999-11-06 22:16 ` 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=5bpuy3v17a.fsf@giga.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
--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).