From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS autolearn=no autolearn_force=no version=3.4.4 Received: from mx2.math.uh.edu (mx2.math.uh.edu [129.7.128.33]) by inbox.vuxu.org (Postfix) with ESMTP id DB4D926B6D for ; Thu, 23 May 2024 02:50:02 +0200 (CEST) Received: from lists1.math.uh.edu ([129.7.128.208]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1s9wee-00000007sSk-0HKX for ml@inbox.vuxu.org; Wed, 22 May 2024 19:50:00 -0500 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.97.1) (envelope-from ) id 1s9wcN-00000004jf4-3f9c for ml@inbox.vuxu.org; Wed, 22 May 2024 19:47:39 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1s9wcL-00000004jev-0fW8 for ding@lists.math.uh.edu; Wed, 22 May 2024 19:47:37 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1s9wcG-00000000k9K-2nQI for ding@lists.math.uh.edu; Wed, 22 May 2024 19:47:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=iCasmJhDWNDuXx3cvRKhwY4A/psg8s8WIBC8hXVhbTY=; b=nhH6cxbHOwV0geVMH7PhtRRsUj FDyDyxNo5WTbcgW8L6DOicUTUZMLd0j3EqrekMq6ZX4Y2kOiaPLAzthl9iCpdoi4Si8bVgSw70fF0 quHOq7P8ek5IXugHZ+l/yPkctaW4c1k8n8HI031DMbrQtJQy9z2vZ375j3KkaUJKpNf4=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s9wc3-0007hU-7U for ding@gnus.org; Thu, 23 May 2024 02:47:22 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1s9wc0-0004vJ-68 for ding@gnus.org; Thu, 23 May 2024 02:47:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org To: ding@gnus.org From: Emanuel Berg Subject: Re: Updating definition of "bogus" groups? Date: Thu, 23 May 2024 02:47:09 +0200 Message-ID: <878r0173si.fsf@dataswamp.org> References: <87zfsi9408.fsf@ericabrahamsen.net> <871q5ufb7a.fsf@eps142.cdf.udc.es> <87msoi6i3f.fsf@dataswamp.org> <87wmnlwygi.fsf@hope.eyrie.org> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:Q8bql6oKqESDF2pYIBjAEpZWY3E= Mail-Copies-To: never List-ID: Precedence: bulk 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. But then I wonder, how do they enter the *Group* buffer in the first place? > 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? Maybe! -- underground experts united https://dataswamp.org/~incal