Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] turnsole alpha preview
Date: Sun, 03 Apr 2011 20:52:08 +0000	[thread overview]
Message-ID: <1301863573-sup-881@masanjin.net> (raw)
In-Reply-To: <AANLkTimv9yUTMQ+Xc8bshBFU-eogs-K-6QVWLY+_J3aY@mail.gmail.com>

Hi Matthieu,

Thanks for the detailed bug reports.

Reformatted excerpts from Matthieu Rakotojaona's message of 2011-04-02:
> >/home/rakoo/src/turnsole/lib/turnsole/ncurses-patches.rb:19:in `block in <module:Curses>': undefined method `color!' for Curses:Module (NoMethodError)

I think this is fixed in the latest turnsole master. Can you please try it?

> >/home/rakoo/src/turnsole/lib/turnsole/accounts.rb:39:in `block in add_account': undefined method `gpgkey' for nil:NilClass (NoMethodError)

Also should be fixed in the latest turnsole master.

> Now with heliotrope, I have the problems with the encoding :
> - When I search for words with "é", I have an error :
> 
> >HeliotropeServer::RequestError - can't parse query: parse error: line 1: syntax error, unexpected $end, expecting WORD:

Good bug! I didn't test this at all. This one I am going to have to spend a
little bit of time on.

> >ArgumentError - invalid byte sequence in UTF-8:
> > /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/parser.rb:217:in `split'

Can you try the latest heliotrope master? I think I've fixed this.

> But I do think everyone should use UTF-8.

I kind of agree. Heliotrope is utf-8 specific. But in Turnsole I am trying to
be nice and support the system encoding.

> In a totallly unrelated note, do you plan on syncing back heliotrope work
> with the maildir directory ? Just to know.

No. Since Heliotrope is a server, I plan on avoiding that class of problem
entirely by a) making it easy to extract your email from Heliotrope, if you
decide to not use it any more, and b) eventually adding an IMAP emulation
layer, if you want to use other clients.

So you would entrust Heliotrope to both store, as well as index, your email, in
whatever way it wants to.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

      reply	other threads:[~2011-04-03 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 18:15 [sup-devel] " William Morgan
2011-04-02 19:00 ` Michael Stapelberg
2011-04-02 20:40   ` William Morgan
2011-04-03 20:44     ` William Morgan
2011-04-02 21:32 ` [sup-talk] " Mariano Mara
2011-04-02 22:39 ` [sup-devel] " Matthieu Rakotojaona
2011-04-03 20:52   ` William Morgan [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=1301863573-sup-881@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --cc=sup-devel@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