From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jamie Forth <J.Forth@gold.ac.uk>
Cc: "31739@debbugs.gnu.org" <31739@debbugs.gnu.org>
Subject: bug#31739: 25.2; Cannot expire articles in virtual group
Date: Sat, 30 Apr 2022 18:24:42 +0200 [thread overview]
Message-ID: <8735huzghh.fsf@gnus.org> (raw)
In-Reply-To: <87ftjpi2c4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 19 Oct 2019 10:09:15 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I just wondered what the value of the variable was. :-) But this shows
> that you definitely have gnus-summary-expire-articles in
> gnus-summary-prepare-exit-hook, so that's not the reason the articles
> aren't expired.
>
> Reading the code, gnus-summary-prepare-exit-hook is called before the
> marks are cleared, so at that point the expirable list should still
> exist, which makes the bug you're seeing even more incomprehensible...
I seemed to have dropped the ball on this one -- this was two years ago.
Jamie, do you still see these problems in recent Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-30 16:24 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
2019-10-19 8:09 ` Lars Ingebrigtsen
2022-04-30 16:24 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735huzghh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=31739@debbugs.gnu.org \
--cc=J.Forth@gold.ac.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.