From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jamie Forth <j.forth@gold.ac.uk>
Cc: 31739@debbugs.gnu.org
Subject: bug#31739: 25.2; Cannot expire articles in virtual group
Date: Sun, 29 Sep 2019 10:21:38 +0200 [thread overview]
Message-ID: <87ftkfseb1.fsf@gnus.org> (raw)
In-Reply-To: <877enb7pqw.fsf@lutyens.i-did-not-set--mail-host-address--so-tickle-me> (Jamie Forth's message of "Wed, 06 Jun 2018 19:07:35 +0100")
Jamie Forth <j.forth@gold.ac.uk> writes:
> Expiring articles within a non-virtual group works as expected, but not
> within a virtual group.
>
> 1. Create a new virtual group (G V)
> 2. Select and add a component group (G v)
> 3. Enter the new virtual group and mark a message as expirable (E)
> 4. Quit the group (or B e) to trigger the expiry process results in
> the following messages
>
> Expiring articles...
> Expiring articles in <component group>...done
> Expiring articles...done
>
> 5. Re-enter the virtual group (or C-u M-g), and find that the article
> previously marked as expirable has not been expired.
>
> I’m using nnimap groups and `nnmail-expiry-wait` is set to immediate.
I'm unable to reproduce this in Emacs 27. If I follow your recipe
(create a virtual group with an nnimap component, and mark an article in
the virtual group with `E'), the IMAP log shows:
10:19:12 [quimby.gnus.org] 7219 SELECT "spam"
10:19:12 [quimby.gnus.org] 7220 UID STORE 392789 +FLAGS.SILENT (\Deleted)
10:19:12 [quimby.gnus.org] 7221 UID EXPUNGE 392789
So the message was deleted from the nnimap component group.
Are you still seeing this bug in newer Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-29 8:21 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 [this message]
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
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=87ftkfseb1.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 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).