From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Articles in nndraft:* no longer always unread
Date: Sat, 18 Sep 2010 09:25:25 +0200 [thread overview]
Message-ID: <874odnikd6.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87y6b0lzj1.fsf@topper.koldfront.dk>
On Sat, 18 Sep 2010 01:29:38 +0200, Adam wrote:
> I seem to remember that articles in nndraft:{drafts,delayed} used to
> automatically return to being unread, so that if something is in one of
> those groups, you would always see the group (and the count).
> I think this behaviour has changed - if I create a draft and read it
> (but do not send it), the drafts group doesn't appear (with 1 article)
> after I get news.
According to a recent bisection (I feel like a surgeon!) this behavior
changed in:
commit 7cce28b2d41e11d65102b8910ee9efc361b720ca
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date: Sat Sep 4 19:15:31 2010 +0200
Add more changes related to the new methodology for requesting backend data.
Best regards,
Adam
--
"It's my chainsaw Adam Sjøgren
Division is mine" asjo@koldfront.dk
next prev parent reply other threads:[~2010-09-18 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 23:29 Adam Sjøgren
2010-09-18 7:25 ` Adam Sjøgren [this message]
2010-09-18 11:58 ` Lars Magne Ingebrigtsen
2010-09-18 12:23 ` Adam Sjøgren
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=874odnikd6.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).