From: Harry Putnam <reader@newsguy.com>
Subject: Re: Agent readedness bug
Date: 24 Sep 1999 15:11:53 -0700 [thread overview]
Message-ID: <m3puz89cye.fsf@satellite.local.lan> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "24 Sep 1999 19:49:36 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > Start gnus ... use `c' (catchup) to mark all nntp groups as read.
> > Press `g' to varify group readedness
> > Go unplugged (`J j') Then accidently - on purpose, hit 'g'
> > Go plugged (`J j') hit `g'
> >
> > On my end, all or nearly all nntp groups will now show hundreds of
> > unread messages.
>
> I don't get this. It kinda sounds like the first `g' you did didn't
> result in the agent's active file getting updated. Is that the case?
That was it yes. I discovered why this was happening when I started
using some functions you posted a while back telling how to start 2
gnus, one off-line, one on-line. The interplay between the two
depends on the active file being read by both. So changing that
setting from nil fixed both.
prev parent reply other threads:[~1999-09-24 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-07 0:03 Harry Putnam
1999-09-24 17:49 ` Lars Magne Ingebrigtsen
1999-09-24 22:11 ` Harry Putnam [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=m3puz89cye.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).