From: col@baibell.org (Colin Bell)
Subject: [sup-talk] [PATCH] Fix for imap based sources
Date: Fri, 02 Nov 2007 12:19:10 +1100 [thread overview]
Message-ID: <1193966225-sup-1066@lankhmar> (raw)
In-Reply-To: <1193962132-sup-5058@silver>
Excerpts from Ian Taylor's message of Fri Nov 02 11:14:55 +1100 2007:
>
> That doesn't seem quite right to me. The RFC seems to state that the
> 'Recent' flag is more of a notification that this is the first session
> to see the message.
>
> What about this instead?
>
> labels = { :Flagged => :starred,
> :Deleted => :deleted
> }.inject(@labels) do |cur, (imap, sup)|
> cur + (state[:flags].include?(imap) ? [sup] : [])
> end
> labels += [:unread] unless state[:flags].include?(:Seen)
>
> Seems like we want to tag it as unread if it isn't marked as 'Seen'.
Works for me. Thanks
next prev parent reply other threads:[~2007-11-02 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 10:25 Marcus Williams
2007-11-02 0:14 ` Ian Taylor
2007-11-02 1:19 ` Colin Bell [this message]
[not found] <0ae09eda00048831@IMSS-WIN>
2007-10-25 12:35 ` Marcus Williams
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=1193966225-sup-1066@lankhmar \
--to=col@baibell.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