keys: add ReadKeys() and UnreadKeys()

[vbatts]

as well as making the Keys() return the collection of both read and unread

Signed-off-by: Vincent Batts vbatts@hashbangbash.com

[luksen]

Hey, thanks for taking an interest! But I don't think this change is a good idea. The current interface enforces the semantic that once the application knows about new messages, they should be in cur. The only reason to get message keys without the move is to violate that.

Also, as it is now, the returned keys won't be of any use since Filename doesn't search new.

[vbatts]

but how are you supposed to access/count/know-of new messages? Even while writing the simplest of tools to show unread count, I could not find a way to access that information.

[luksen]

The information whether a user has seen/read a message is encoded in the flags. So to count those you have to call Unseen to make sure all messages are known to the application. And then go through all keys returned by Keys and use Flags to count those that have S set.

A long running application can use Unseen to incrementally update its internal state, but for small tools it makes sense to just call it once at the start.

[luksen]

@vbatts: I added UnseenCount(). It might address your problem. (Haven't really tested it, so there might be kinks)

[vbatts]

Oh neat. Thanks

…

On Thu, Jan 18, 2018, 08:13 luksen ***@***.***> wrote: @vbatts <https://github.com/vbatts>: I added UnseenCount(). It might address your problem. (Haven't really tested it, so there might be kinks) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF6QhQYYwqBaHI-c3XyJVaZ8IkdyTVks5tL0OHgaJpZM4DH96I> .