From: Jaap-Henk Hoepman <hoepman@cs.utwente.nl>
Subject: Re: Gnus 5.8.2: group list
Date: 06 Dec 1999 09:54:18 +0100 [thread overview]
Message-ID: <kp1z90ih51.fsf@utip151.cs.utwente.nl> (raw)
In-Reply-To: Brian May's message of "06 Dec 1999 11:43:50 +1100"
On 06 Dec 1999 11:43:50 +1100 Brian May <bmay@csse.monash.edu.au> writes:
> >>>>> "Jack" == Jack Vinson <vinson@unagi.cis.upenn.edu> writes:
>
> Jack> I will sometimes see one of my groups show up in duplicate.
> Jack> (Sometimes in the same topic, sometimes as the top-level
> Jack> topic.) When I C-k it from one location it also vanishes
> Jack> from the other location. I can easily C-y it back into its
> Jack> correct place.
>
> Jack> This is where things get funny. If I do a new 'l', then a
> Jack> /different/ group will show up as a duplicate.
>
> I saw similar behaviour in PGnus 0.97 and PGnus 0.98.
>
> I was about to report a bug, but then I accidently pushed the wrong
> button, and resorted the list of groups (IIRC). I have never seen the
> problem since.
>
> When the problem occurred for me, Gnus never displayed the number of
> articles for the first duplicate entry - instead it put a "*". This
> duplicate entry was always right at the top, unless I move it
> elsewhere.
This also happened to me today after upgrading from pgnus 0.96 to gnus 5.8.2.
What's the right way to fix it?
Jaap-Henk
--
Jaap-Henk Hoepman | Come sail your ships around me
Dept. of Computer Science | And burn these bridges down
University of Twente | Nick Cave - "Ship Song"
Email: hoepman@cs.utwente.nl === WWW: www.cs.utwente.nl/~hoepman
Phone: +31 53 4893795 === Secr: +31 53 4893770 === Fax: +31 53 4894590
PGP ID: 0xF52E26DD Fingerprint: 1AED DDEB C7F1 DBB3 0556 4732 4217 ABEF
next prev parent reply other threads:[~1999-12-06 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-05 5:50 Jack Vinson
1999-12-06 0:43 ` Brian May
1999-12-06 8:54 ` Jaap-Henk Hoepman [this message]
1999-12-06 18:38 ` François Pinard
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=kp1z90ih51.fsf@utip151.cs.utwente.nl \
--to=hoepman@cs.utwente.nl \
/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).