Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: HEADS UP: Largely rewritten gnus-agent implementation.
Date: Sat, 23 Nov 2002 21:27:44 +0100	[thread overview]
Message-ID: <84y97kav5r.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uadk0ceos.fsf@adobe.com>

Danny Siu <dsiu@adobe.com> writes:

> 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.

Yes, thanks a lot, Kevin.

> - 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.

I don't notice this.  I use splitting with nnimap and I have the same
setting, but split articles are not marked as read.

I have seen mark-as-read when entering a group, but I fixed that as I
described.

> - .agentview files may contain bogus info, like "nil 2" etc.  (or it has a
>   new format now?)

nil means it's empty, 2 means it's in format 2.  Yes, Kevin has
introduced a new format.  The new format supports ranges and also
includes the history file information, so that the history file is
not needed anymore.

> - 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.

I use dormant articles rarely.  Let me test this with an nnimap group.

> thanks for the good work, Kevin and Kai!

My work consisted of writing the ChangeLog entry.  Kudos to Kevin,
not to me.

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



  reply	other threads:[~2002-11-23 20:27 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
2002-11-23 20:27   ` Kai Großjohann [this message]
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=84y97kav5r.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).