Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: how to kill a virtual group
Date: Fri, 28 Jan 2022 14:21:52 -0800	[thread overview]
Message-ID: <87czkbmrgf.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r18ro9py.fsf@mat.ucm.es>

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Uwe Brauer <oub@mat.ucm.es> 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.



  reply	other threads:[~2022-01-28 22:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 15:07 Uwe Brauer
2022-01-28 17:05 ` Eric Abrahamsen
2022-01-28 21:02   ` Uwe Brauer
2022-01-28 22:21     ` Eric Abrahamsen [this message]
2022-01-29  0:03       ` Emanuel Berg
2022-01-29  4:18         ` Eric Abrahamsen
2022-01-29 15:48           ` Emanuel Berg
2022-01-29 17:17             ` Eric Abrahamsen
2022-01-30 22:33               ` Emanuel Berg
2022-01-31 19:24                 ` Eric Abrahamsen
2022-01-31 21:59                   ` Emanuel Berg
2022-02-01  1:43                     ` Eric Abrahamsen
2022-02-01  3:10                       ` Emanuel Berg
2022-02-01  4:32                         ` Eric Abrahamsen
2022-02-01  7:26                           ` Emanuel Berg
2022-02-01 16:10                             ` Eric Abrahamsen
2022-02-04  2:30                               ` Emanuel Berg
2022-02-04 16:12                                 ` 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=87czkbmrgf.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).