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 10:25:33 -0700	[thread overview]
Message-ID: <87wmnlwygi.fsf@hope.eyrie.org> (raw)
In-Reply-To: <87msoi6i3f.fsf@dataswamp.org> (Emanuel Berg's message of "Wed, 22 May 2024 16:23:32 +0200")

Emanuel Berg <incal@dataswamp.org> writes:

> But instead of getting confused by terminology, which is always going to
> be incorrect to some degree in any applied endeavor, if we are talking
> `gnus-check-bogus-newsgroups', what is that it does that is useful? What
> to do, or not do for that matter, should be based on that.

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?

My experience is that when a newsgroup that I'm reading is removed, it
shows up with a * for the article count, so it's pretty obvious that it's
been deleted and I can either delete the corresponding group in Gnus or
investigate what's going on.  But maybe there are scenarios that involve
hidden groups where it makes sense to explicitly check for these?

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


  reply	other threads:[~2024-05-22 17:26 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 [this message]
2024-05-23  0:47       ` Emanuel Berg
2024-05-23  2:30         ` Russ Allbery
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=87wmnlwygi.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).