From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: expiring in nnselect groups not saved
Date: Thu, 05 May 2022 08:39:09 +0800 [thread overview]
Message-ID: <87o80c6ceq.fsf@ust.hk> (raw)
In-Reply-To: <8735hp0y2b.fsf@ecocode.net>
>>>>> "EC" == Erik Colson <eco@ecocode.net> writes:
EC> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Andy made this possible in a commit a couple of months ago (also
>> requires setting `nnselect-allow-ephemeral-expiry' to a non-nil
>> value), so unless you're running from master (which isn't a
>> terrible idea), you might not have this yet.
EC> Thanks for the info, it solves another problem I had ;)
EC> I have that variable and now messages get expired when I leave
EC> an nnselect group.
EC> But what I asked for is saving the expiry marks I add while in a
EC> nnselect group, which still doesn't seem to work with that
EC> variable set to t.
Then this would be a bug :) I don't have a lot of time at the moment,
but when I do I'll take a look. If you are comfortable with debugging
the relevant code is in nnselect-push-info. There is an iterative loop
over gnus-article-mark-lists (which includes the expirable mark) which
should be doing the work.
Does it work with a single group (if its specific to multiple groups
that would be relevant info)?
--
Andrew Cohen
next prev parent reply other threads:[~2022-05-05 0:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 1:17 set up Gnus to work with a remote system mailserver (with Dovecot?) Emanuel Berg
2022-04-07 2:34 ` Byung-Hee HWANG
2022-04-07 3:08 ` Emanuel Berg
2022-04-07 7:47 ` Andreas Schwab
2022-04-07 8:07 ` Emanuel Berg
2022-04-07 8:12 ` Emanuel Berg
2022-04-07 8:27 ` Emanuel Berg
2022-04-10 11:47 ` Byung-Hee HWANG
2022-04-10 13:13 ` Emanuel Berg
2022-04-11 3:47 ` Byung-Hee HWANG
2022-04-11 4:03 ` Byung-Hee HWANG
2022-04-11 22:55 ` Bob Newell
2022-04-12 2:18 ` Byung-Hee HWANG
2022-04-12 8:30 ` Eric S Fraga
2022-04-12 6:00 ` Emanuel Berg
2022-04-12 6:34 ` Emanuel Berg
2022-04-19 23:53 ` Emanuel Berg
2022-04-20 0:11 ` Emanuel Berg
2022-04-21 12:38 ` Byung-Hee HWANG
2022-04-21 13:16 ` Emanuel Berg
2022-04-21 13:30 ` Byung-Hee HWANG
2022-04-21 13:41 ` Emanuel Berg
2022-04-27 20:15 ` Emanuel Berg
2022-04-27 20:27 ` Emanuel Berg
2022-04-28 3:44 ` Byung-Hee HWANG
2022-05-03 2:36 ` Emanuel Berg
2022-05-03 6:36 ` Byung-Hee HWANG
2022-05-03 7:01 ` Emanuel Berg
2022-05-03 7:17 ` Byung-Hee HWANG
2022-05-04 0:11 ` Emanuel Berg
2022-05-04 11:50 ` expiring in nnselect groups not saved Erik Colson
2022-05-04 17:01 ` Eric Abrahamsen
2022-05-04 21:47 ` Erik Colson
2022-05-05 0:39 ` Andrew Cohen [this message]
2022-05-05 0:48 ` Andrew Cohen
2022-05-05 2:07 ` Andrew Cohen
2022-05-05 10:10 ` Erik Colson
2022-05-05 10:48 ` Erik Colson
2022-05-05 11:09 ` Erik Colson
2022-05-05 11:21 ` Erik Colson
2022-05-05 12:20 ` Erik Colson
2022-05-05 20:59 ` Erik Colson
2022-05-06 0:49 ` Andrew Cohen
2022-05-06 15:42 ` Erik Colson
2022-05-06 16:27 ` Erik Colson
2022-04-07 8:51 ` set up Gnus to work with a remote system mailserver (with Dovecot?) Uwe Brauer
2022-04-07 8:58 ` Emanuel Berg
2022-04-07 10:28 ` Eric S Fraga
2022-04-07 16:43 ` Russ Allbery
2022-04-08 10:03 ` Eric S Fraga
2022-04-08 11:59 ` Emanuel Berg
2022-04-07 9:31 ` Christian Barthel
2022-04-07 10:57 ` Emanuel Berg
2022-04-09 23:23 ` Emanuel Berg
2022-04-21 1:42 ` Emanuel Berg
2022-04-21 2:52 ` Emanuel Berg
2022-04-21 2:54 ` Emanuel Berg
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=87o80c6ceq.fsf@ust.hk \
--to=acohen@ust.hk \
--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).