From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [bug] NoMemoryError on huge mbox
Date: Mon, 02 Jun 2008 19:34:04 -0700 [thread overview]
Message-ID: <1212460371-sup-5830@entry> (raw)
In-Reply-To: <188c71690806011026u55851e39k2dd982dae28621d@mail.gmail.com>
Reformatted excerpts from Gabriel Landais's message of 2008-06-01:
> I'm not able to load my Thunderbird mbox into sup. Added my Inbox
> mbox with sup-add/sup-config :
Interesting. This error seems to occur during a string construction.
Others have reported weird problems with Thunderbird mbox files before,
and I now suspect there's something screwy about their mbox format.
Like, they use \r instead of \n for linebreaks. Which wouldn't make any
fucking sense at all, but who knows.
Can you post the output of a
ruby -e 'p File.open("Inbox").read(1000)'
so we can take a look at what these guys are doing? (Or whatever
Thunderbird file you want instead of "Inbox".)
Thanks!
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-06-03 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 17:26 Gabriel Landais
2008-06-03 2:34 ` William Morgan [this message]
2008-06-03 8:09 ` Gabriel Landais
2008-06-04 2:42 ` 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=1212460371-sup-5830@entry \
--to=wmorgan-sup@masanjin.net \
/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