Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: gnus marks nonexistent articles (was: nnmaildir's article counts are better now)
Date: Sat, 07 Dec 2002 21:40:54 -0500	[thread overview]
Message-ID: <m3bs3xtepf.fsf_-_@multivac.cwru.edu> (raw)
In-Reply-To: <87el8udfql.fsf@mail.paradoxical.net> (Josh Huber's message of "Fri, 06 Dec 2002 16:01:06 -0500")

I think I've figured it out now.  When Gnus finds that an article does
not exist, it marks it as read.  But nnmaildir doesn't store marks for
nonexistent articles.  (Does nnimap?  nnml?)
nnmaildir-request-update-info returns only the marks it knows about;
it removes marks supplied by Gnus that weren't stored by nnmaildir.
So after it's called, all the nonexistent articles seem to exist as
unread, as far as Gnus is concerned.  Even if nnmaildir is the only
backend currently affected by this problem, I think it makes sense to
fix this in Gnus:  gnus-request-update-info could artificially add
(1 . (1- min)) to the read range after getting marks from the backend.
Thoughts?  Objections?  Other ideas?


paul



  reply	other threads:[~2002-12-08  2:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 17:41 nnmaildir's article counts are better now Paul Jarc
2002-12-06 19:36 ` Josh Huber
2002-12-06 19:42   ` Paul Jarc
2002-12-06 19:53     ` Josh Huber
2002-12-06 20:09       ` Paul Jarc
2002-12-06 21:01         ` Josh Huber
2002-12-08  2:40           ` Paul Jarc [this message]
2002-12-08  5:38             ` gnus marks nonexistent articles Simon Josefsson
2002-12-09  5:50               ` Paul Jarc
2002-12-09  9:44                 ` Simon Josefsson
2002-12-09 19:42                 ` Paul Jarc

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=m3bs3xtepf.fsf_-_@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).