Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: JR Boyens <jboyens@fooninja.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] try heliotrope!
Date: Mon, 27 Jun 2011 08:56:59 -0400	[thread overview]
Message-ID: <1309179117-sup-9518@marvin.local> (raw)
In-Reply-To: <1309152077-sup-5963@masanjin.net>

Excerpts from William Morgan's message of 2011-06-27 01:36:24 -0400:
> Hi guys,
> 
> If any of you are interested in trying out the next generation of Sup, I
> have things in a reasonably stable state. It's still too early for a
> gem, but I have updated the README for both client and server sides. So
> if you'd like to run some highly experimental code and see what the
> future of curses-based email might look like, follow the instructions
> in:
> 
> http://github.com/wmorgan/heliotrope
>   and then
> http://github.com/wmorgan/turnsole
> 
> Lots of stuff is broken, but I have been using it as an end-to-end email
> system for a week or so now, so the basics are there. Tell me how it goes!

Seems to work rather good when I can get the messages into heliotrope...

GMail import seems to work great.

I keep having this issue with the Maildirs I use with Sup:


; loading mail...
; scanning 1 directories...
; found 2623 messages
; reading in dates...
; warning: no date in /Users/jboyens/Mail/Work/INBOX/cur/1302957166_2.57311.marvin.local,U=11400,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,S
; warning: no date in /Users/jboyens/Mail/Work/INBOX/cur/1302957167_0.57311.marvin.local,U=10933,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,
/Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:50:in `block in get_date_in_file': invalid byte sequence in UTF-8 (ArgumentError)
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:48:in `open'
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:48:in `get_date_in_file'
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:40:in `block in get_files'
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:40:in `map'
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:40:in `get_files'
	from /Users/jboyens/heliotrope/lib/heliotrope/maildir-walker.rb:12:in `load!'
	from ./bin/heliotrope-add:123:in `<main>'


I've tried a few maildirs and it seems endemic. The file that it has an
issue with contains a single, solitary, lower-case h.


Any ideas?
--
JR Boyens
jboyens@fooninja.org
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2011-06-27 13:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  5:36 [sup-devel] " William Morgan
2011-06-27 12:56 ` JR Boyens [this message]
2011-06-29  4:12   ` [sup-talk] " William Morgan
2011-06-27 15:02 ` Kevin Mark
2011-06-27 21:30 ` sergeig
2011-06-28  3:54   ` William Morgan
2011-06-28  6:32     ` Sergei
2011-06-28 22:10       ` William Morgan
2011-06-27 23:52 ` Andrés
2011-06-29  4:02   ` William Morgan
2011-06-29 19:47     ` Andrés
2011-06-29 20:29       ` Matthieu Rakotojaona
2011-06-29 21:35         ` William Morgan
2011-06-28  3:32 ` [sup-devel] " 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=1309179117-sup-9518@marvin.local \
    --to=jboyens@fooninja.org \
    --cc=sup-talk@rubyforge.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