From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3116 invoked from network); 28 Jan 2022 22:22:16 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 28 Jan 2022 22:22:16 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nDZdG-004O5t-EF for ml@inbox.vuxu.org; Fri, 28 Jan 2022 16:22:14 -0600 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94.2) (envelope-from ) id 1nDZdF-003ecn-Pb for ml@inbox.vuxu.org; Fri, 28 Jan 2022 16:22:13 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1nDZdE-003ech-Om for ding@lists.math.uh.edu; Fri, 28 Jan 2022 16:22:12 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nDZdC-00CJle-MO for ding@lists.math.uh.edu; Fri, 28 Jan 2022 16:22:12 -0600 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=Jpyr2AR12Z0HxVQN1JVcXGLQKPvkS3wNsGCCxOc/Uzg=; b=hGQvP/d8UBVkJs/wMtWgFhPpUm xkyLRERkdcNuvLZdqJgckQkq4cqgQsTF4LfgGoN9MVvu4xz0J2eenpmZ6lu8BDIxfQIt3CmqkXPj/ OyY8qE4G7AijAazWFrniDtNWCh1OuU6V1pWAcemxCfiJ4Ayw5PgPL0/JDgc6fJuODFTg=; 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 1nDZd4-0007dL-Tv for ding@gnus.org; Fri, 28 Jan 2022 23:22:05 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nDZd2-0004Ly-0K for ding@gnus.org; Fri, 28 Jan 2022 23:22:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: how to kill a virtual group Date: Fri, 28 Jan 2022 14:21:52 -0800 Message-ID: <87czkbmrgf.fsf@ericabrahamsen.net> References: <87a6ffx5jg.fsf@mat.ucm.es> <874k5nokor.fsf@ericabrahamsen.net> <87r18ro9py.fsf@mat.ucm.es> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cancel-Lock: sha1:j5KVutQdioXjbbjfrJ2IaJoZR50= List-ID: Precedence: bulk Uwe Brauer writes: >>>> "EA" == Eric Abrahamsen writes: > >> Uwe Brauer writes: >>> Hi >>> >>> In my group buffer I have >>> >>> * 0: nnvirtual:Annu21 >>> >>> When I kill this group, it disappears, but when I leave gnus restart >>> emacs and start gnus again it pops again. > >> I don't know, I can't reproduce this. It's possible that you need to >> activate the group (just enter it) before you can "really" delete it? > > I will try this again Do let me know what happens. >>> My server buffer shows >>> >>> {nnvirtual:^$\|\(^nnimap\+UCMgmail:1-Annu21$\)\|\(^nnimap\+UCMgmail:INBOX$\)} (opened) >>> >>> But I cannot delete that group neither. > >> Do you get the error "Server XYZ must be deleted from your configuration >> files"? That's what I see, and it's definitely a bug, as it's exactly >> opposite from reality. > > Precisely this is the error I see! [1] Okay, this is something I've looked at several times over the past couple years. I am not sure how to fix it mostly because I don't understand the original intended behavior of variables like `gnus-server-alist' and `gnus-inserted-opened-servers'. I'll probably need to open a bug report and get Lars looking at it, and figure out first what the code *should* do, before actually fixing it. > Footnotes: > [1] Hm lately I found two bugs, that one and the one concerning the > registry labels (restrict the summary buffer to message with those > labels). Anyhow I should better fix them (if I knew how...) I've got some code underway for the registry marks issue, but it will probably take a little while to finish it.