From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Remove Ghost groups
Date: Wed, 27 May 2020 12:31:12 -0400 [thread overview]
Message-ID: <87v9khe3vz.fsf@local.lan> (raw)
In-Reply-To: <87pnatuhzd.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Harry Putnam <reader@newsguy.com> writes:
>>>
>>>> [NOTE: this message is probably a duplicate of a previous post where I
>>>> forget to include the Image I intended to attach]
>>>>
>>>> I have developed a number of what might be called ghost groups. Some
>>>> (most) are as the result of removing groups behind gnus back. Others,
>>>> I'm not sure of their origin.
>>>>
>>>> These groups now appear in gnus -> groups buffer with an asterisk
>>>> before them as in the included image below.
>>>>
>>>> They do not respond to simple C-k nor do they respond to C-u G del
>>>
>>> Can you tell us the backend of the groups, and also what happens when
>>> you hit C-k? Is there a message of any kind?
>>
>> When I hit C-k the pointer goes into `working' mode and never
>> returns. When I force it with C-g all but one nntp group disappears
>> and I have to press `l' to get the full setup back
>>
>> checking the Messages-buffer it only shows
>>
>> *beep*
>> Quit
>
> Can you `toggle-debug-on-quit', do it again, and post the backtrace?
Sorry for making you work too hard to help. I should have included
backtraces from the start ...
Included below:
Backtrace from quiting with C-k on nnml and nnimap. Also backtrace
from quitting on C-u G <bkspc> on nnimap
------- ------- ---=--- ------- -------
Backtrace from nnml group with C-k . . . followed by C-g
Debugger entered--Lisp error: (quit)
gnus-group-goto-group("nnml: AdamSj\303\270gren")
gnus-topic-change-level("nnml: AdamSj\303\270gren" 9 3 nil)
gnus-group-change-level((nil ("nnml: AdamSj\303\270gren" 3 nil nil "nnml:")) 9 nil)
gnus-group-kill-group(nil nil)
gnus-topic-kill-group(nil)
funcall-interactively(gnus-topic-kill-group nil)
call-interactively(gnus-topic-kill-group nil nil)
command-execute(gnus-topic-kill-group)
------- --------- ---=--- --------- --------
Backtrace from nnimap group with C-k . . . followed by C-g
Debugger entered--Lisp error: (quit)
gnus-group-goto-group("nnimap+hput3:INBOX.Gas-South")
gnus-topic-change-level("nnimap+hput3:INBOX.Gas-South" 9 3 nil)
gnus-group-change-level((nil ("nnimap+hput3:INBOX.Gas-South" 3 ((1 . 2)) ((unexist)) "nnimap:hput3" ((modseq . "37742") (uidvalidity . "1495544836") (active 1 . 2) (permanent-flags %Answered %Flagged %Draft %Deleted %Seen $X-ME-Annot-2 $IsMailingList $IsNotification $HasAttachment $HasTD %*)))) 9 nil)
gnus-group-kill-group(nil nil)
gnus-topic-kill-group(nil)
funcall-interactively(gnus-topic-kill-group nil)
call-interactively(gnus-topic-kill-group nil nil)
command-execute(gnus-topic-kill-group)
------- --------- ---=--- --------- --------
Backtrace from C-u G <bkspc> on nnimap group followed by C-g
Debugger entered: ("Quit")
nnimap-wait-for-response(93)
nnimap-get-response(93)
nnimap-command("DELETE %S" "INBOX.lists")
nnimap-request-delete-group("INBOX.lists" (4) "hput3")
gnus-request-delete-group("nnimap+hput3:INBOX.lists" (4))
gnus-group-delete-group("nnimap+hput3:INBOX.lists" (4))
funcall-interactively(gnus-group-delete-group "nnimap+hput3:INBOX.lists" (4))
call-interactively(gnus-group-delete-group nil nil)
command-execute(gnus-group-delete-group)
next prev parent reply other threads:[~2020-05-27 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 14:42 Harry Putnam
2020-05-20 16:28 ` Adam Sjøgren
2020-05-24 16:38 ` Harry Putnam
2020-05-20 16:38 ` Eric Abrahamsen
2020-05-24 16:32 ` Harry Putnam
2020-05-24 21:43 ` Eric Abrahamsen
2020-05-27 16:31 ` Harry Putnam [this message]
2020-05-27 22:03 ` Eric Abrahamsen
2020-05-30 18:04 ` Harry Putnam
2020-06-01 16:43 ` Harry Putnam
2020-06-01 17:21 ` Eric Abrahamsen
2020-05-20 16:48 ` Dan Christensen
2020-05-24 16:36 ` Harry Putnam
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 14:38 Remove ghost groups Harry Putnam
2020-05-20 13:59 Harry Putnam
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=87v9khe3vz.fsf@local.lan \
--to=reader@newsguy.com \
--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).