From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Remove Ghost groups
Date: Sun, 24 May 2020 12:36:35 -0400 [thread overview]
Message-ID: <874ks5e1d8.fsf@local.lan> (raw)
In-Reply-To: <87367uft88.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> On May 20, 2020, Harry Putnam <reader@newsguy.com> wrote:
>
>> I have developed a number of what might be called ghost groups. Some
>> (most) are as the result of removing groups behind gnus back. Others,
>> I'm not sure of their origin.
>>
>> These groups now appear in gnus -> groups buffer with an asterisk
>> before them as in the included image below.
>>
>> They do not respond to simple C-k nor do they respond to C-u G del
>>
>> How can I get rid of them?
>
> Does gnus-group-check-bogus-groups help? It's bound to `b' in the
> *Group* buffer. For me, it generates an error about a nil select
> method, but maybe you'll have better luck...
For me, when I press `b' I see `checking bogus newsgroups' and the
pointer goes into eternal `working' mode. When forced with
C-g... the messages-buffer shows:
Checking bogus newsgroups...
*beep*
Quit
next prev parent reply other threads:[~2020-05-24 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 14:42 Harry Putnam
2020-05-20 16:28 ` Adam Sjøgren
2020-05-24 16:38 ` Harry Putnam
2020-05-20 16:38 ` Eric Abrahamsen
2020-05-24 16:32 ` Harry Putnam
2020-05-24 21:43 ` Eric Abrahamsen
2020-05-27 16:31 ` Harry Putnam
2020-05-27 22:03 ` Eric Abrahamsen
2020-05-30 18:04 ` Harry Putnam
2020-06-01 16:43 ` Harry Putnam
2020-06-01 17:21 ` Eric Abrahamsen
2020-05-20 16:48 ` Dan Christensen
2020-05-24 16:36 ` Harry Putnam [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 14:38 Remove ghost groups Harry Putnam
2020-05-20 13:59 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=874ks5e1d8.fsf@local.lan \
--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).