Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Question about article identification and backends.
Date: Mon, 19 May 2003 12:47:29 -0400	[thread overview]
Message-ID: <m3brxyg9xk.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <84d6ig1szu.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Sun, 18 May 2003 11:52:53 +0200")

kai.grossjohann@gmx.net (Kai Großjohann) wrote:
> It seems that the current problem is: say you have read all of the
> articles in a certain group, that is, articles 1 through 100.  Now
> you move an article numbered 42 into that group.  It is unread.
> Then Gnus will think it is read.
>
> But it ought to be possible to tweak Gnus so that it just splits the
> read sequence from 1-100 into 1-41,43-100.

If all articles from 1 to 100 already exist, and we are inserting a
new article at position 42, then the new read list is 1-41,43-101.
The positions of all the later articles have to be changed.  Since
articles are currently *identified* by position, this is more work
than just a tweak.

> Maybe it is even possible using the backend interface: the backend
> could tell Gnus the new list 1-41,43-100 of read articles.

That's (sort of) how nnmaildir used to do it.  But it breaks the
agent, the cache, and 'seen marks, at least.


paul



  parent reply	other threads:[~2003-05-19 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 19:56 Rob Browning
2003-05-17 21:29 ` Andreas Fuchs
2003-05-18  2:57   ` Rob Browning
2003-05-18  3:19   ` Rob Browning
2003-05-18  9:52     ` Kai Großjohann
2003-05-18 18:38       ` Rob Browning
2003-05-18 18:50         ` Rob Browning
2003-05-19 13:02           ` Kai Großjohann
2003-05-19 13:02         ` Kai Großjohann
2003-05-19 16:57         ` Paul Jarc
2003-05-19 16:47       ` Paul Jarc [this message]
2003-05-19 20:49         ` Kai Großjohann
2003-05-19 20:57           ` Paul Jarc
2003-05-20 10:56             ` Kai Großjohann
2003-05-20 17:33           ` Rob Browning
2003-05-22  7:04             ` 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=m3brxyg9xk.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).