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: Mon, 07 Oct 2019 05:16:50 +0200 [thread overview]
Message-ID: <87d0f9ckil.fsf@gnus.org> (raw)
In-Reply-To: <87d0fcfjh0.fsf@gold.ac.uk> (Jamie Forth's message of "Fri, 4 Oct 2019 18:34:20 +0000")
Jamie Forth <J.Forth@gold.ac.uk> writes:
> Stepping through gnus-group-expire-articles-1,
> expirable is nil.
>
> The value returned from (gnus-info-marks info) is:
>
> ((seen (22 . 40)) (unexist (1 . 34)))
>
> So the expirable marks are getting dropped somehow?
Sounds like it.
For my test group, I get:
(assq 'expire (gnus-info-marks (gnus-get-info "nnvirtual:imap-test")))
=> (expire 392790 394237)
You get nil for yours?
I've looked through the code for something special being done with the
expirable marks, and I can't find anything that's nixing out those in
particular. But I may be looking in the wrong parts of the code...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-07 3:16 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 [this message]
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=87d0f9ckil.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).