Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Sever expunged /agent viewable?
Date: 14 Jul 1999 18:11:13 -0700	[thread overview]
Message-ID: <m3r9ma67ke.fsf@satellite.local.lan> (raw)


Am I the "Lone Ranger" on this:

I've carefully noted the oldest viewable articles in gnu.emacs.gnus
(agentized and downloaded with a predicate of "true" [all]), twice
now since the release of '0.91 (now running '0.95).  I've put comments
in Group params indicating the oldest articles dates.  After a few
days those articles disappear from Gnus view just as before 0.91.

Example:  Yesterday I entered (unplugged) gnu.emacs.gnus with `C-u
<RET>'.  The oldest articles on display were Jun 13-14.  Today I enter
the same group after downloading `J s' to agent.  Enter gnu.emacs.gnus
with C-u <RET>.  The oldest viewable articles are Jun 26.

Everthing from Jun  13-14 to Jun 26 is now invisible  but still in the
directory.  This is  not supposed to happen anymore.   

Lars has suggested that my setup is hosed: 

>  Message-ID: <m3so6z8vos.fsf@quimbies.gnus.org>
  Harry Putnam <reader@newsguy.com> writes:

> > Or are you saying that only messages downloaded by "91" or later will
> > be kept visible? 

 Lars writes:
> No, but it sounds (from your other posts) like there's something
> seriously wrong with your Agent setup, I think.

Are other users seeing the behavior described above or is gnus
displaying your (expunged from server articles) as advertised?
 
As it happens, the NNTP server I use, shows the same message being the
oldest as does my gnu.emacs.gnus (agentized) group.

Newsgroups: gnu.emacs.gnus
Subject: Re: pop3.el and hanging emacs
From: John Saylor <jsaylor@mediaone.net>
Message-ID: <m34sjvxi48.fsf@office.saylor.bogus>



             reply	other threads:[~1999-07-15  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-15  1:11 Harry Putnam [this message]
1999-08-27 18:51 ` Lars Magne Ingebrigtsen
1999-08-28  0:01   ` Harry Putnam

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=m3r9ma67ke.fsf@satellite.local.lan \
    --to=reader@newsguy.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).