From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] Newline Issues
Date: Sat, 29 Mar 2008 05:02:31 -0500 [thread overview]
Message-ID: <1206784905-sup-8496@chris-tablet> (raw)
In-Reply-To: <1206549226-sup-8056@south>
Excerpts from William Morgan's message of Wed Mar 26 11:40:24 -0500 2008:
> Reformatted excerpts from Christopher Warrington's message of 2008-03-03:
> > When I use offlineimap under Cgywin, the messages are delivered with
> > CRLF. Sup cannot parse these: it thinks that the body is empty. I know
> > that sup is seeing the entire message. If I press H, I see all of the
> > message.
>
> I've finally had a chance to look into this. I've just patched Sup to
> handle carriage returns in mbox files, but things are still broken
> because of RubyMail.
>
> It looks like there's an outstanding RubyMail patch here:
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=2821&group_id=446&atid=17
> 56
>
> If you apply that and get the latest git, I think things should work.
That appears to have done it. All is well in Cygwin land, for now.
--
Christopher Warrington <chrisw at rice.edu>
prev parent reply other threads:[~2008-03-29 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 9:33 Christopher Warrington
2008-03-26 16:40 ` William Morgan
2008-03-29 10:02 ` Christopher Warrington [this message]
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=1206784905-sup-8496@chris-tablet \
--to=chrisw@rice.edu \
/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