Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: No longer can enter groups! (Re: Pterodactyl Gnus v0.82 is released)
Date: 17 Apr 1999 20:35:00 -0400	[thread overview]
Message-ID: <ltd8129363.fsf@asfast.com> (raw)
In-Reply-To: Lloyd Zusman's message of "17 Apr 1999 20:24:54 -0400"

Lloyd Zusman <ljz@asfast.com> writes:

> [ ... ]
>
> I have just installed pgnus-0.82 after having been running pgnus-0.81.
> Everything runs fine when I use version 0.81, but in 0.82, I cannot
> enter any groups, even when they are listed in the Group buffer as
> having unread articles.  I try to enter the group (via the spacebar or
> the enter key), and a message comes out at the bottom of the screen
> saying that the expiry process is taking place, and then the group is
> not entered with the cursor moving down to the next group with unread
> articles.  The unread article count remains the same after this
> happens.

Another thing: I get the 'no unread articles' message as this is
occurring, even though the unread article count for the group still
shows the same positive number after this happens.  When I switch
back to 0.81 and try to enter the same groups, the unread article
count shows up the same way in the Group buffer, and when I enter
the group, that many unread articles are indeed being displayed in
the Summary buffer.

> [ ... ]

-- 
 Lloyd Zusman
 ljz@asfast.com


  reply	other threads:[~1999-04-18  0:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-17 16:42 Pterodactyl Gnus v0.82 is released Lars Magne Ingebrigtsen
1999-04-17 17:50 ` Michael Cook
1999-04-18  6:26   ` Lars Magne Ingebrigtsen
1999-04-18  0:24 ` No longer can enter groups! (Re: Pterodactyl Gnus v0.82 is released) Lloyd Zusman
1999-04-18  0:35   ` Lloyd Zusman [this message]
1999-04-19  1:36   ` No longer can enter groups in 0.82 and 0.83 ... ??? Lloyd Zusman
1999-04-19  2:33     ` Lloyd Zusman
1999-04-19  6:26       ` Lars Magne Ingebrigtsen

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=ltd8129363.fsf@asfast.com \
    --to=ljz@asfast.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).