From: Danny Siu <dsiu@adobe.com>
Subject: Re: HEADS UP: Largely rewritten gnus-agent implementation.
Date: Sun, 24 Nov 2002 02:40:35 +0800 [thread overview]
Message-ID: <uadk0ceos.fsf@adobe.com> (raw)
In-Reply-To: <84bs4ggtnq.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Sat, 23 Nov 2002 17:03:37 +0100")
I am only using nnnil as primary and nnimap as secondary backend. I removed
all .fetched files, did a 'gnus-agent-regenerate', and 'J s'
- gnus-agent-regenerate seems to do the right finally: it recreates
.agentview based on articles that have already been download on disk. This
alone saved me hours of agent refetching time! Thanks for making this
works.
- i have (setq gnus-agent-mark-unread-after-downloaded nil) but sometimes
articles are marked read ('O') after being splitted to the its destination
group.
- .agentview files may contain bogus info, like "nil 2" etc. (or it has a
new format now?)
- i am seeing all my dormanted articles became read (marked 'O')!!! I know
that nnimap stores gnus specific marks, like dormant, on IMAP servers that
support custom marks. this is a major problem for agent right now.
agent is working much better than before and i am seeing some operations are
much faster too.
thanks for the good work, Kevin and Kai!
Kai Großjohann writes:
Kai> Kevin Greiner did a really great job, I think, of improving
Kai> gnus-agent and making it more efficient, too. I kind of forgot what
Kai> exactly he has changed, but I can say the following:
Kai> * The old .fetched files that I introduced are not needed anymore.
Kai> * gnus-agent-consider-all-articles is supported properly.
Kai> There is a sanity check in there which invokes (debug), so if you see
Kai> that, please report it to Kevin and/or me, with some information
Kai> about what you were seeing. After gathering the data (especially the
Kai> contents of the backtrace buffer), it should be safe to just
Kai> continue, the mess will be cleaned up automatically.
Kai> The ChangeLog entries are from me, they are probably bogus to some
Kai> degree. This can be sorted out later, though.
Kai> Kevin is gone over the weekend and he suggested that I wait with
Kai> committing this, but I'm too excited to wait!
Kai> Ah, maybe I should mention some gotcha. With previous versions of
Kai> the code (but not the one I'm checking in!) I saw that articles were
Kai> marked as read when entering the group and they appeared to be gone.
Kai> If this happens, don't panik. Instead, do C-x u from the group
Kai> buffer (gnus-undo, to revert the marking as read), then use `J u' on
Kai> the group to fetch it, then try to enter the group again. This
Kai> worked reliably to make the articles reappear when I tried it. (The
Kai> problem only happens in plugged mode.) I don't think that you will
Kai> see this, but just in case...
Kai> I think that's it! Please report your findings.
Kai> kai -- ~/.signature is: umop ap!sdn (Frank Nobis)
--
Danny Siu
next prev parent reply other threads:[~2002-11-23 18:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 16:03 Kai Großjohann
2002-11-23 18:40 ` Danny Siu [this message]
2002-11-23 20:27 ` Kai Großjohann
2002-11-23 20:32 ` Kai Großjohann
2002-11-23 18:45 ` Danny Siu
2002-11-23 20:29 ` Kai Großjohann
2002-11-24 15:32 ` Danny Siu
2002-11-24 16:02 ` Danny Siu
2002-11-25 3:07 ` Henrik Enberg
2002-11-25 16:55 ` Henrik Enberg
2002-11-25 20:26 ` Kai Großjohann
2002-11-26 2:29 ` Kevin Greiner
2002-11-26 7:28 ` Kai Großjohann
2002-11-24 8:43 ` Denis Yakovlev
2002-11-26 3:09 ` Kevin Greiner
2002-11-24 13:02 ` Mark Triggs
2002-11-24 14:08 ` Kai Großjohann
2002-11-24 14:27 ` Mark Triggs
2002-11-25 7:28 ` Kai Großjohann
2002-11-25 14:42 ` Mark Triggs
2002-11-25 14:48 ` Kai Großjohann
2002-11-25 16:41 ` Kevin Greiner
2002-11-25 20:23 ` Kai Großjohann
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=uadk0ceos.fsf@adobe.com \
--to=dsiu@adobe.com \
/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).