Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] [PATCH] More IMAP/Maildir functionality
Date: Fri, 02 Nov 2007 12:18:19 +0000	[thread overview]
Message-ID: <1194005479-sup-2005@tomsk> (raw)

Hi -

This patch cleans up my last IMAP patch, and adds the
each_raw_message_line method to both Maildir and IMAP so that you dont
get an exception when you try to save a message to a file with an IMAP
or maildir source. I cant test the Maildir version works easily, so if
someone else could that would be good. If I get time I'll get around
to testing the Maildir stuff, just not now as I dont use it :)

This fixes the unread status problem to use the lack of /Seen properly
and adds the marked_read? methods to all sources.

Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: source-diffs
Type: application/octet-stream
Size: 4527 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071102/a3d8a87c/attachment-0001.obj 


             reply	other threads:[~2007-11-02 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 12:18 Marcus Williams [this message]
2007-11-05  3:15 ` William Morgan
2007-11-05  9:54   ` Marcus Williams
2007-11-05 15:44     ` William Morgan

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=1194005479-sup-2005@tomsk \
    --to=marcus-sup@quintic.co.uk \
    /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