From: reader@newsguy.com
To: ding@gnus.org
Subject: Re: (gnus-group-list-all-matching) bug?
Date: Sat, 05 Jan 2008 16:47:22 -0600 [thread overview]
Message-ID: <87bq7zc39x.fsf@newsguy.com> (raw)
In-Reply-To: <84ir27vs6i.fsf@incoming.verizon.net>
Dave Goldberg <david.goldberg6@verizon.net> writes:
[...]
>
>> That is, not a single group is displayed.. instead the topics all
>> close up and all I see is a neat assembly of the topics.
>
> I am unable to repeat this. When I enter a search to A M, I get any
> matching groups and their topics. All other topics are hidden, but
> that may be the result of my hiding empty topics as a preference.
>
Well thats good news I guess.
Gack.. it just so happens that the first 3 groups I thought of that
weren't visible had actually been killed. Maybe quite some time
ago... maybe even on a different machine.
I should have tried a few that were actually visible already to make
sure.
I tried `web' (I once had 2 of those)
I tried `ford' (I had two ford truck groups once upon a time)
I tried `kde' (Had 3 of those...)
I just knew I still had some of those.
When I saw your post, tried the obvious thing (groups I could see) and
it worked just like it should.
I'm not sure what brought up all the goofy stuff. I don't see it now
but then I went through it when it came up and killed it all off.
There is one thing there I notice and I guess you say its probably
normal.
After running `A M' if you open a topic with no hits displayed it
rolls out all the groups under there. In my case I hit the nnml topic
and rolled out literally 150+ groups. Many have not seen the light of
day for years. (but none were killed or zombied at least)
prev parent reply other threads:[~2008-01-05 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 16:22 reader
2008-01-05 22:11 ` Dave Goldberg
2008-01-05 22:47 ` reader [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=87bq7zc39x.fsf@newsguy.com \
--to=reader@newsguy.com \
--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).