Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Remove Ghost groups
Date: Wed, 20 May 2020 09:38:40 -0700	[thread overview]
Message-ID: <87a722a7e7.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87imgqy8f4.fsf@local.lan> (Harry Putnam's message of "Wed, 20 May 2020 10:42:39 -0400")

Harry Putnam <reader@newsguy.com> writes:

> [NOTE: this message is probably a duplicate of a previous post where I
> forget to include the Image I intended to attach]
>
> 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

Can you tell us the backend of the groups, and also what happens when
you hit C-k? Is there a message of any kind?


  parent reply	other threads:[~2020-05-20 16:39 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 [this message]
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
  -- 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=87a722a7e7.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=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).