From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: upgrade notes
Date: Fri, 04 Feb 2011 12:29:38 -0800 [thread overview]
Message-ID: <sdoc6r1r2l.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <87hbcj8znm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 04 Feb 2011 09:42:21 -0800")
>>>>> On Fri, 04 Feb 2011 09:42:21 -0800, Lars Ingebrigtsen <larsi@gnus.org> said:
LI> Oh, right. Otherwise everything is OK? It's showing the correct number
LI> of messages and everything?
Yep. The unread number gets updated.
LI> The % mark is something that I must admit I can't recall ever hearing
LI> about, even though "git blame" claims that I added it in 1998. So it's
LI> supposed to appear on groups that have new mail after you do a `g'?
LI> That sounds quite useful, actually. :-)
It is (err... was)...
LI> Is this correct? The `%' would stay there over several `g' runs? I may
LI> be misreading the code.
Yep. That's correct. If I enter the group, but don't read anything,
and exit it would go away.
Functionally it was an "indication that new mail was in the group since
the last time I had been in it".
LI> 1) Ignore the issue. "% is for client-side splits"
:-(
LI> 2) Have nnimap follow the semantics for the other mail backends, and add
LI> a dummy thing to nnmail-split-history if a `g' registers new messages.
LI> Simple enough to do.
That sounds like it would work. I think. Since I'm not familiar with
how splitting in gnus is done (I used it once back in like, um, 1960 I
think) I'm not sure if that sentence meets my functionality described
above or not.
LI> 3) Add a new ?W spec (or something) that would just show a "%" on
LI> all groups with unseen messages.
I *think* that's right too. I have lots of "unread" messages in groups
because I typically will go into a box, read something and then "unmark"
it again because I need to deal with it later (where read-marks are left
on stuff that is "don't delete yet, but it's not functionally a
todo-list item").
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://pontifications.hardakers.net/
next prev parent reply other threads:[~2011-02-04 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 16:31 Wes Hardaker
2011-02-04 17:04 ` Lars Ingebrigtsen
2011-02-04 17:27 ` Wes Hardaker
2011-02-04 17:42 ` Lars Ingebrigtsen
2011-02-04 20:29 ` Wes Hardaker [this message]
2011-02-07 10:25 ` Lars Ingebrigtsen
2011-02-07 16:43 ` Wes Hardaker
2011-02-07 18:37 ` Wes Hardaker
2011-02-07 20:42 ` Eric S Fraga
2011-02-07 21:12 ` Wes Hardaker
2011-02-06 18:29 ` Reiner Steib
2011-02-07 9:58 ` Lars Ingebrigtsen
2011-02-05 17:07 ` Steinar Bang
2011-02-07 16:45 ` Wes Hardaker
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=sdoc6r1r2l.fsf@wjh.hardakers.net \
--to=wes@hardakers.net \
--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).