Gnus development mailing list
 help / color / mirror / Atom feed
From: Eze Ogwuma <typhoon@dircon.co.uk>
Cc: ding@gnus.org
Subject: Re: Gnus keeps fetching read Articles from the Server
Date: 25 Jan 1998 11:25:28 +0000	[thread overview]
Message-ID: <m3afck6biv.fsf@localhost.localdomain> (raw)
In-Reply-To: Felix Lee's message of "Sat, 24 Jan 1998 20:57:23 -0800"

Felix Lee <flee@teleport.com> writes:

> > [Synopsis] With gnus-asynchronous, gnus-keep-backlog and
> > gnus-use-cache all set Gnus still re-reads selected articles from the
> > server when they have previously been viewed with X u or MIME decoded.
> 
> yup.  I noticed this a while ago and didn't get around to
> tracking it down until now.

Thanks.

I was starting to think I was in peoples score files.

> the problem is, gnus gives articles to gnus-backlog only if
> it fetched the article directly.  any articles that come out
> of gnus-async don't make it into the backlog.

[...]


-- 
Eze Ogwuma


      reply	other threads:[~1998-01-25 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-08  7:12 Eze Ogwuma
1998-01-25  4:57 ` Felix Lee
1998-01-25 11:25   ` Eze Ogwuma [this message]

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=m3afck6biv.fsf@localhost.localdomain \
    --to=typhoon@dircon.co.uk \
    --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).