From: Jamie Forth <J.Forth@gold.ac.uk>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "31739@debbugs.gnu.org" <31739@debbugs.gnu.org>
Subject: bug#31739: 25.2; Cannot expire articles in virtual group
Date: Fri, 18 Oct 2019 13:13:19 +0000 [thread overview]
Message-ID: <877e52nqmp.fsf@gold.ac.uk> (raw)
In-Reply-To: <878spik8ti.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 18 Oct 2019 05:54:01 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Let's see... Here's the call sequence I get when I `E' and then `q'
> from the nnvirtual group:
>
> Debugger entered: nil
> nnimap-request-expire-articles((392790 394237 394238) "spam" "quimby.gnus.org" nil)
> gnus-request-expire-articles((392790 394237 394238) "nnimap+quimby.gnus.org:spam")
> gnus-group-expire-articles-1("nnimap+quimby.gnus.org:spam")
> nnvirtual-request-expire-articles((392790 394237 394238 394330) "imap-test" "^$\\|\\(^nnimap\\+quimby\\.gnus\\.org:spam$\\)" nil)
> gnus-request-expire-articles((392790 394237 394238 394330) "nnvirtual:imap-test")
> gnus-summary-expire-articles()
> run-hooks(gnus-summary-prepare-exit-hook)
> apply(run-hooks gnus-summary-prepare-exit-hook)
> gnus-run-hooks(gnus-summary-prepare-exit-hook)
> gnus-summary-exit()
> funcall-interactively(gnus-summary-exit)
>
> So this is done from gnus-summary-prepare-exit-hook. What's the value
> of that hook for you?
Not sure I’m doing the right thing here… setting `debug-on-entry` for
`gnus-summary-prepare-exit-hook` and stepping through I see this.
Debugger entered--returning value: nil
#f(compiled-function (&optional now) "Expire all articles that are marked as expirable in the current group." (interactive nil) #<bytecode 0x15590511b8b9>)()
* apply(#f(compiled-function (&optional now) "Expire all articles that are marked as expirable in the current group." (interactive nil) #<bytecode 0x15590511b8b9>) nil)
* gnus-summary-expire-articles()
run-hooks(gnus-summary-prepare-exit-hook)
apply(run-hooks gnus-summary-prepare-exit-hook)
gnus-run-hooks(gnus-summary-prepare-exit-hook)
gnus-summary-exit()
funcall-interactively(gnus-summary-exit)
call-interactively(gnus-summary-exit nil nil)
command-execute(gnus-summary-exit)
And going a bit deeper…
Debugger entered--entering a function:
* apply(message ("Expiring articles in %s..." "nnimap+gold:Junk Email"))
* gnus-message(6 "Expiring articles in %s..." "nnimap+gold:Junk Email")
* gnus-group-expire-articles-1("nnimap+gold:Junk Email")
* nnvirtual-request-expire-articles((13) "vg-test" "^nnimap\\+gold:Junk Email$" nil)
* gnus-request-expire-articles((13) "nnvirtual:vg-test")
* #f(compiled-function (&optional now) "Expire all articles that are marked as expirable in the current group." (interactive nil) #<bytecode 0x15590511b8b9>)()
* apply(#f(compiled-function (&optional now) "Expire all articles that are marked as expirable in the current group." (interactive nil) #<bytecode 0x15590511b8b9>) nil)
* gnus-summary-expire-articles()
run-hooks(gnus-summary-prepare-exit-hook)
apply(run-hooks gnus-summary-prepare-exit-hook)
gnus-run-hooks(gnus-summary-prepare-exit-hook)
gnus-summary-exit()
funcall-interactively(gnus-summary-exit)
call-interactively(gnus-summary-exit nil nil)
command-execute(gnus-summary-exit)
Sorry if that wasn’t what you meant.
--
Jamie
next prev parent reply other threads:[~2019-10-18 13:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 18:07 bug#31739: 25.2; Cannot expire articles in virtual group Jamie Forth
2019-09-29 8:21 ` Lars Ingebrigtsen
2019-09-30 17:00 ` Jamie Forth
2019-10-01 12:25 ` Lars Ingebrigtsen
2019-10-01 12:27 ` Lars Ingebrigtsen
2019-10-01 14:08 ` Jamie Forth
2019-10-03 15:51 ` Lars Ingebrigtsen
2019-10-04 18:34 ` Jamie Forth
2019-10-07 3:16 ` Lars Ingebrigtsen
2019-10-07 16:18 ` Jamie Forth
2019-10-14 6:35 ` Lars Ingebrigtsen
2019-10-16 11:50 ` Jamie Forth
2019-10-18 3:54 ` Lars Ingebrigtsen
2019-10-18 13:13 ` Jamie Forth [this message]
2019-10-19 8:09 ` Lars Ingebrigtsen
2022-04-30 16:24 ` Lars Ingebrigtsen
2022-05-29 13:19 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e52nqmp.fsf@gold.ac.uk \
--to=j.forth@gold.ac.uk \
--cc=31739@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).