From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Removing the expirable mark
Date: Wed, 07 Sep 2011 09:30:37 -0400 [thread overview]
Message-ID: <8762l4jx8i.fsf@uwo.ca> (raw)
In-Reply-To: <87pqnf3fi4.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Wed, 18 May 2011 11:23:25 -0400 Dan Christensen <jdc@uwo.ca> wrote:
>
> DC> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> So when synchronizing the marks in "news" backends, we should convert
>>> expirable marks to read marks?
>
> DC> Either that or: if a group doesn't support deletion, change the key
> DC> binding so that read marks get added instead of expirable marks.
>
> DC> I'd be quite happy with either option. It would also be good if
> DC> expirable marks that are already in the .newsrc.eld got converted
> DC> to read marks.
>
> My way would convert expirable marks automatically so it's probably
> cleaner. I just need to learn how to actually do it (hints and help
> welcome :)
I saw that Lars disabled auto-expire for read-only groups, but I'm
still having the problem that my nntp groups have lots of expirable
marks, since I often manually mark articles expirable by hand. Does
anyone have any idea which function to hack so that expirable marks
get converted to read marks?
Dan
next prev parent reply other threads:[~2011-09-07 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:29 Didier Verna
2011-05-11 21:40 ` Ted Zlatanov
2011-05-13 19:09 ` Dan Christensen
2011-05-13 20:11 ` Ted Zlatanov
2011-05-14 2:18 ` Dan Christensen
2011-05-16 18:39 ` Ted Zlatanov
2011-05-18 15:23 ` Dan Christensen
2011-05-18 20:44 ` Ted Zlatanov
2011-09-07 13:30 ` Dan Christensen [this message]
2011-09-10 19:56 ` Lars Magne Ingebrigtsen
2011-09-11 23:23 ` Dan Christensen
2011-09-12 4:24 ` Lars Magne 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=8762l4jx8i.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).