Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: Updating definition of "bogus" groups?
Date: Wed, 22 May 2024 19:30:54 -0700	[thread overview]
Message-ID: <87pltdmf8h.fsf@hope.eyrie.org> (raw)
In-Reply-To: <878r0173si.fsf@dataswamp.org> (Emanuel Berg's message of "Thu, 23 May 2024 02:47:09 +0200")

Emanuel Berg <incal@dataswamp.org> writes:
> Russ Allbery wrote:

>> I've never been clear on what this function does that I would want to
>> do and why it's bound to a key. I've only run it when I pressed b by
>> mistake, and it's never done anything. I may just be not using the part
>> of Gnus where it would be useful?

> The docstring says "Remove bogus newsgroups." which, granted, sounds
> pretty useful.

Historically on Usenet that means newsgroups that were deleted, so I
assume that's what it was intended to mean.

> But then I wonder, how do they enter the *Group* buffer in the first
> place?

Well, if it's just groups that were deleted, one either was subscribed to
them or for whatever reason had them listed and unsubscribed.

In other news readers historically, it was common to keep a newsrc that
included every group on the server whether one was subscribed or not.  In
that context, checking for bogus groups was looking for groups that you
have listed in your newsrc (possibly unsubscribed) that no longer exist.

I guess Gnus could have the same problem?  It definitely doesn't with my
settings, but I know there are a bunch of settings.

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>


  reply	other threads:[~2024-05-23  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 22:47 Eric Abrahamsen
2024-05-22  9:27 ` Alberto Luaces
2024-05-22 14:23   ` Emanuel Berg
2024-05-22 17:25     ` Russ Allbery
2024-05-23  0:47       ` Emanuel Berg
2024-05-23  2:30         ` Russ Allbery [this message]
2024-05-23  3:54           ` Eric Abrahamsen

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=87pltdmf8h.fsf@hope.eyrie.org \
    --to=eagle@eyrie.org \
    --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).