Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Removing the expirable mark
Date: Mon, 16 May 2011 13:39:37 -0500	[thread overview]
Message-ID: <87liy65w2e.fsf@lifelogs.com> (raw)
In-Reply-To: <87fwoi10uy.fsf@uwo.ca>

On Fri, 13 May 2011 22:18:13 -0400 Dan Christensen <jdc@uwo.ca> wrote: 

DC> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Fri, 13 May 2011 15:09:49 -0400 Dan Christensen <jdc@uwo.ca> wrote: 
>> 
DC> This doesn't answer your question, but I also find that because of my
DC> habit of using expiry in mail groups, I often accidentally mark articles
DC> as expirable in nntp groups as well, which doesn't make sense.  Maybe
DC> Gnus should automatically convert expirable marks to read marks in nntp
DC> groups (and other groups which don't allow article deletion)?  My
DC> .newsrc.eld gets really cluttered because of my misbehaving fingers.
>> 
>> I think Gnus does that when the marks are actually saved.

DC> Not for me.  Here's a snippet from my .newsrc.eld:

DC>     ("nntp+news.gmane.org:gmane.linux.ubuntu.news" 3
DC>    ((1 . 313))
DC>    ((seen (1 . 313)) (forward 160 188) (expire 175 (186 . 188) 191 197 207 (273 . 275) 308))

So when synchronizing the marks in "news" backends, we should convert
expirable marks to read marks?

Is that OK?  Can you think of any reason not to do this?  It seems safe
to me.

Ted




  reply	other threads:[~2011-05-16 18:39 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 [this message]
2011-05-18 15:23         ` Dan Christensen
2011-05-18 20:44           ` Ted Zlatanov
2011-09-07 13:30             ` Dan Christensen
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=87liy65w2e.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).