sup

community/pipermail-archives/sup-devel/2010-11.txt (82644B) - raw

 From sup-bugs@masanjin.net  Thu Nov  4 07:02:53 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Thu, 04 Nov 2010 11:02:53 +0000
 Subject: [sup-devel] [issue125] sup-mail broke
 In-Reply-To: <1288868572.96.0.0451510169956.issue125@masanjin.net>
 Message-ID: <1288868572.96.0.0451510169956.issue125@masanjin.net>
 
 
 New submission from anonymous:
 
 sup-mail
 [Thu Nov 04 16:26:59 +0530 2010] WARNING: can't find character set by using 
 locale, defaulting to utf-8
 [Thu Nov 04 16:28:53 +0530 2010] ERROR: oh crap, an exception
 ----------------------------------------------------------------
 I'm very sorry. It seems that an error occurred in Sup. Please
 accept my sincere apologies. Please submit the contents of
 /home/jagadeesh/.sup/exception-log.txt and a brief report of the
 circumstances to http://masanjin.net/sup-bugs/ so that I might
 address this problem. Thank you!
 
 Sincerely,
 William
 ----------------------------------------------------------------
 --- NoMethodError from thread: poll after loading inbox
 undefined method `[]' for nil:NilClass
 /usr/lib/ruby/1.8/sup/xapian_index.rb:572:in `mkterm'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:347:in `find_docid'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:353:in `find_doc'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:363:in `get_entry'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:77:in `build_message'
 /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:372:in `synchronize'
 /usr/lib/ruby/1.8/sup/xapian_index.rb:77:in `build_message'
 /usr/lib/ruby/1.8/sup/index.rb:236:in `send'
 /usr/lib/ruby/1.8/sup/index.rb:236:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:110:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:169:in `each_message_from'
 /usr/lib/ruby/1.8/sup/maildir.rb:160:in `each'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `upto'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `each'
 /usr/lib/ruby/1.8/sup/util.rb:599:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:599:in `__pass'
 /usr/lib/ruby/1.8/sup/util.rb:586:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:157:in `each_message_from'
 /usr/lib/ruby/1.8/sup/poll.rb:109:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:97:in `each'
 /usr/lib/ruby/1.8/sup/poll.rb:97:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:96:in `synchronize'
 /usr/lib/ruby/1.8/sup/poll.rb:96:in `do_poll'
 /usr/lib/ruby/1.8/sup/util.rb:559:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:559:in `method_missing'
 /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
 /usr/lib/ruby/1.8/sup/poll.rb:47:in `poll_with_sources'
 /usr/lib/ruby/1.8/sup/poll.rb:62:in `poll'
 /usr/lib/ruby/1.8/sup/util.rb:559:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:559:in `method_missing'
 /usr/bin/sup-mail:224
 /usr/lib/ruby/1.8/sup.rb:76:in `reporting_thread'
 /usr/lib/ruby/1.8/sup.rb:74:in `initialize'
 /usr/lib/ruby/1.8/sup.rb:74:in `new'
 /usr/lib/ruby/1.8/sup.rb:74:in `reporting_thread'
 /usr/bin/sup-mail:224
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:674:in `call'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:674
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:615:in `call'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:615:in 
 `load_n_threads_background'
 /usr/lib/ruby/1.8/sup.rb:76:in `reporting_thread'
 /usr/lib/ruby/1.8/sup.rb:74:in `initialize'
 /usr/lib/ruby/1.8/sup.rb:74:in `new'
 /usr/lib/ruby/1.8/sup.rb:74:in `reporting_thread'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:613:in 
 `load_n_threads_background'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:684:in 
 `__unprotected_load_threads'
 (eval):12:in `load_threads'
 /usr/bin/sup-mail:224
 
 ----------
 messages: 297
 nosy: anonymous
 priority: bug
 ruby_version: ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]
 status: unread
 sup_version: 0.10.2
 title: sup-mail broke
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue125>
 _________________________________________
 
 From eg@gaute.vetsj.com  Thu Nov  4 09:21:20 2010
 From: eg@gaute.vetsj.com (Gaute Hope)
 Date: Thu, 04 Nov 2010 14:21:20 +0100
 Subject: [sup-devel] [PATCH] More UTF-8 support; load all labels as UTF-8
 Message-ID: <1288876769-sup-4049@qwerzila>
 
 Even if the labels.txt file is read as UTF-8 apparantly after a label is
 symoblized, it will be US-ASCII on .to_s if possible. This patch forces
 UTF-8.
 
 If you use L to select a US-ASCII label (i.e. Sent) then want to narrow
 the search by pressing L again and use tab to match against an UTF-8
 label sup crashes.
 
 Also fixes one whitespace error in bin/sup
 ---
  bin/sup           |    4 +++-
  lib/sup/buffer.rb |    2 +-
  2 files changed, 4 insertions(+), 2 deletions(-)
 
 diff --git a/bin/sup b/bin/sup
 index fd1dde8..10be161 100755
 --- a/bin/sup
 +++ b/bin/sup
 @@ -49,7 +49,7 @@ No variables.
  No return value.
  EOS
  
 -Redwood::HookManager.register "shutdown", <<EOS 
 +Redwood::HookManager.register "shutdown", <<EOS
  Executes when sup is shutting down. May be run when sup is crashing,
  so don\'t do anything too important. Run before the label, contacts,
  and people are saved.
 @@ -299,6 +299,8 @@ begin
        SearchResultsMode.spawn_from_query "is:unread"
      when :list_labels
        labels = LabelManager.all_labels.map { |l| LabelManager.string_for l }
 +      labels = labels.each { |l| l.force_encoding 'UTF-8' if l.methods.include?(:encoding) }
 +
        user_label = bm.ask_with_completions :label, "Show threads with label (enter for listing): ", labels
        unless user_label.nil?
          if user_label.empty?
 diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
 index f3cfb8a..c36ca56 100644
 --- a/lib/sup/buffer.rb
 +++ b/lib/sup/buffer.rb
 @@ -454,7 +454,7 @@ EOS
    def ask_with_completions domain, question, completions, default=nil
      ask domain, question, default do |s|
        s.force_encoding 'UTF-8' if s.methods.include?(:encoding)
 -      completions.select { |x| x =~ /^#{Regexp::escape s}/i }.map { |x| [x, x] }
 +      completions.select { |x| x =~ /^#{Regexp::escape s}/iu }.map { |x| [x, x] }
      end
    end
  
 -- 
 1.7.3.2
 
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-More-UTF-8-support-load-all-labels-as-UTF-8.patch
 Type: application/octet-stream
 Size: 2061 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101104/cd3ed621/attachment.obj>
 
 From cjparsons1@yahoo.co.uk  Thu Nov  4 11:49:03 2010
 From: cjparsons1@yahoo.co.uk (Chris Parsons)
 Date: Thu, 04 Nov 2010 15:49:03 +0000
 Subject: [sup-devel] [PATCH] 'u' in thread-view-mode copies URL to X
 	selection
 Message-ID: <1288885683-sup-601@chris-eee>
 
 I know there's been some discussion about opening URLs from e-mails in Sup, and
 because many people use Sup via an SSH session, client-side solutions are not
 universally useful... but here is a patch that seems to copy a URL on the
 currently highlighted line to the X selection buffer. (From there I use Kupfer
 http://kaizer.se/wiki/kupfer/ to open the link in a web client.)
 Obviously you can do something similar with a mouse but I use a
 netbook and try to avoid using the trackpad if I can.
 
 It relies on having the program xsel available in your path.
 
 I've never fiddled in Ruby before so accept my apologies if the lines are
 ridiculous, and also if this has been done before by others.
 
 For the reasons I mention (not universal, requires xsel) I don't
 expect it to make it into the Sup code base but I put it out here in
 case it suits anyone else.
 ---
  lib/sup/modes/line-cursor-mode.rb |   13 +++++++++++++
  1 files changed, 13 insertions(+), 0 deletions(-)
 
 diff --git a/lib/sup/modes/line-cursor-mode.rb b/lib/sup/modes/line-cursor-mode.rb
 index 1cae994..e65cbee 100644
 --- a/lib/sup/modes/line-cursor-mode.rb
 +++ b/lib/sup/modes/line-cursor-mode.rb
 @@ -8,6 +8,7 @@ class LineCursorMode < ScrollMode
      k.add :cursor_down, "Move cursor down one line", :down, 'j'
      k.add :cursor_up, "Move cursor up one line", :up, 'k'
      k.add :select, "Select this item", :enter
 +    k.add :selurl, "Copy URL to selection", 'u'
    end
  
    attr_reader :curpos
 @@ -90,6 +91,18 @@ protected
      set_cursor_pos botline - 1 if @curpos > botline - 1
    end
  
 +  def selurl
 +     regex = /(?:http|https|mailto):\/\/\S+/i
 +     this_line = self[curpos][0][1]
 +     match = regex.match(this_line)
 +     return if not match
 +
 +     output = pipe_to_process("xsel -i") do |stream|
 +        stream.print match
 +     end
 +     BufferManager.flash "selected url #{match}"
 +  end
 +
    def cursor_down
      call_load_more_callbacks buffer.content_height if @curpos >= lines - [buffer.content_height/2,1].max
      return false unless @curpos < lines - 1
 -- 
 1.7.3.2
 
 From rlane@club.cc.cmu.edu  Thu Nov  4 12:03:59 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Thu, 04 Nov 2010 12:03:59 -0400
 Subject: [sup-devel] [PATCH] More UTF-8 support; load all labels as UTF-8
 In-Reply-To: <1288876769-sup-4049@qwerzila>
 References: <1288876769-sup-4049@qwerzila>
 Message-ID: <1288886612-sup-8205@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Thu Nov  4 12:04:23 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Thu, 04 Nov 2010 12:04:23 -0400
 Subject: [sup-devel] [PATCH] Bugfix: mime_encode: Encode _ as =5F
 	instead of =96
 In-Reply-To: <1288044796-sup-6774@midna.zekjur.net>
 References: <1288044796-sup-6774@midna.zekjur.net>
 Message-ID: <1288886647-sup-5714@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Thu Nov  4 12:04:49 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Thu, 04 Nov 2010 12:04:49 -0400
 Subject: [sup-devel] [PATCH] Stop double quoting the protocol when
 	sending encrypted emails
 In-Reply-To: <AANLkTimk4yTtJxDj5+H4HfjthdPLQtvE=9enx6GQykRo@mail.gmail.com>
 References: <AANLkTimk4yTtJxDj5+H4HfjthdPLQtvE=9enx6GQykRo@mail.gmail.com>
 Message-ID: <1288886673-sup-9342@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Thu Nov  4 12:05:35 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Thu, 04 Nov 2010 12:05:35 -0400
 Subject: [sup-devel] Message#text_to_chunks performance
 In-Reply-To: <1288264300-sup-7747@tilus.net>
 References: <1288264300-sup-7747@tilus.net>
 Message-ID: <1288886709-sup-7087@zyrg.net>
 
 Excerpts from Tero Tilus's message of Thu Oct 28 08:05:33 -0400 2010:
 > Is the patch-to-mailinglist still the preferred flow of contribution
 > as stated in Wiki?  http://sup.rubyforge.org/wiki/wiki.pl?Contributing
 
 Yes, please send patches to the list.
 
 From alvherre@alvh.no-ip.org  Thu Nov  4 13:54:55 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Thu, 04 Nov 2010 14:54:55 -0300
 Subject: [sup-devel] [PATCH] 'u' in thread-view-mode copies URL to X
 	selection
 In-Reply-To: <1288885683-sup-601@chris-eee>
 References: <1288885683-sup-601@chris-eee>
 Message-ID: <1288893256-sup-8304@alvh.no-ip.org>
 
 Excerpts from Chris Parsons's message of jue nov 04 12:49:03 -0300 2010:
 > I know there's been some discussion about opening URLs from e-mails in Sup, and
 > because many people use Sup via an SSH session, client-side solutions are not
 > universally useful... but here is a patch that seems to copy a URL on the
 > currently highlighted line to the X selection buffer. (From there I use Kupfer
 > http://kaizer.se/wiki/kupfer/ to open the link in a web client.)
 > Obviously you can do something similar with a mouse but I use a
 > netbook and try to avoid using the trackpad if I can.
 
 It seems like this should be more generally doable with a hook.
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 
 From michael+sup@stapelberg.de  Fri Nov  5 06:37:49 2010
 From: michael+sup@stapelberg.de (Michael Stapelberg)
 Date: Fri, 05 Nov 2010 11:37:49 +0100
 Subject: [sup-devel] [PATCH] 'u' in thread-view-mode copies URL to X
 	selection
 In-Reply-To: <1288885683-sup-601@chris-eee>
 References: <1288885683-sup-601@chris-eee>
 Message-ID: <1288953383-sup-1045@midna.zekjur.net>
 
 Hi Chris,
 
 Excerpts from Chris Parsons's message of 2010-11-04 16:49:03 +0100:
 > I know there's been some discussion about opening URLs from e-mails in Sup, and
 > because many people use Sup via an SSH session, client-side solutions are not
 > universally useful... but here is a patch that seems to copy a URL on the
 Not sure which side you mean with client-side now, but I usually want to open
 the URL on the computer I am currently using (not always the side on which sup
 is running, but always the side on which my terminal is running). For that, I
 use the mark-and-yank plugin for urxvt:
 
 http://www.jukie.net/bart/blog/urxvt-url-yank
 
 Best regards,
 Michael
 
 From sup-bugs@masanjin.net  Sat Nov  6 07:45:46 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Sat, 06 Nov 2010 11:45:46 +0000
 Subject: [sup-devel] [issue126] exception at the first poll after a message
 	has been sent
 In-Reply-To: <1289043945.99.0.911687811063.issue126@masanjin.net>
 Message-ID: <1289043945.99.0.911687811063.issue126@masanjin.net>
 
 
 New submission from anonymous:
 
 sup throws the exception below at the first poll after I have sent a message.
 
 This is the setup: I'm fetching mail with offlineimap to a maildir. Sent mails
 go to the maildir "Gesendet", so offlineimap pushes them to my mail server:
 :sent_source: maildir:/home/mkl/Mail/Gesendet
 
 The before-poll hook runs offlineimap
 
 if (@last_fetch || Time.at(0)) < Time.now - 120
   say "Running offlineimap..."
   cmd = "offlineimap -q -u Noninteractive.Basic"
   `#{cmd} 2>&1`
   say "Finished offlineimap run."
 end
 @last_fetch = Time.now
 
 For completeness, here the offlineimaprc:
 [general]
 accounts = mkl
 ui = TTY.TTYUI
 
 [Account mkl]
 localrepository = Local
 remoterepository = Remote
 
 [Repository Local]
 type = Maildir
 localfolders = ~/Mail
 
 [Repository Remote]
 type = IMAP
 remotehost = xxx
 remoteuser = xxx
 ssl=yes
 remotepass=xxx
 
 The exception is:
 --- NoMethodError from thread: user-invoked poll
 undefined method `[]' for nil:NilClass
 /usr/lib/ruby/1.8/sup/index.rb:722:in `mkterm'
 /usr/lib/ruby/1.8/sup/index.rb:500:in `find_docid'
 /usr/lib/ruby/1.8/sup/index.rb:506:in `find_doc'
 /usr/lib/ruby/1.8/sup/index.rb:516:in `get_entry'
 /usr/lib/ruby/1.8/sup/index.rb:193:in `build_message'
 /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
 /usr/lib/ruby/1.8/sup/index.rb:525:in `synchronize'
 /usr/lib/ruby/1.8/sup/index.rb:193:in `build_message'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:117:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:176:in `each_message_from'
 /usr/lib/ruby/1.8/sup/maildir.rb:160:in `each'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `upto'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `each'
 /usr/lib/ruby/1.8/sup/util.rb:610:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:610:in `__pass'
 /usr/lib/ruby/1.8/sup/util.rb:597:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:164:in `each_message_from'
 /usr/lib/ruby/1.8/sup/poll.rb:116:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:104:in `each'
 /usr/lib/ruby/1.8/sup/poll.rb:104:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:103:in `synchronize'
 /usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
 /usr/lib/ruby/1.8/sup/poll.rb:50:in `poll_with_sources'
 /usr/lib/ruby/1.8/sup/poll.rb:69:in `poll'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/bin/sup-mail:330
 /usr/lib/ruby/1.8/sup.rb:75:in `reporting_thread'
 /usr/lib/ruby/1.8/sup.rb:73:in `initialize'
 /usr/lib/ruby/1.8/sup.rb:73:in `new'
 /usr/lib/ruby/1.8/sup.rb:73:in `reporting_thread'
 /usr/bin/sup-mail:330
 
 ----------
 messages: 299
 nosy: anonymous
 priority: bug
 ruby_version: 1.8
 status: unread
 sup_version: 0.11
 title: exception at the first poll after a message has been sent
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue126>
 _________________________________________
 
 From dmishd@gmail.com  Sat Nov  6 16:08:01 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Sat, 6 Nov 2010 20:08:01 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 Message-ID: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 
 I often find that loading long threads of encrypted messages (I have
 several of over 10 messages and one of nearly 40) leads to lots of
 flickering as the console replaces sup, sup comes back, the console
 comes back again ... It is also very slow, and involves writing
 decrypted messages to disk (if only temporarily) which could be a
 security hole. So I've looked about and found the gpgme gem which
 provides an API to use, and allows decryption entirely in memory.
 
 So I've rewritten lib/sup/crypto.rb to use gpgme. The functionality is
 pretty much the same. Things I'm aware of that are different:
 
 * we can't set the signature algorithm, so we have to use whatever is
 set in the user's preferences
 * the gpg-args hook has been replaced by the gpg-options hook
 
 Other than that I think it is the same, although it took some work to
 get the signature output to be the same. The other main difference is
 that it's much faster and nicer now :)
 
 It could do with some testing - I don't have much in the way of
 messages that cause gpg to complain, so if you do, please try opening
 those messages with this code and see if the behaviour is reasonable -
 no crashes, given messages about why your message was bad etc.
 
 Also I guess I should ask if people are happy to use this gem. Is it
 hard to use on Macs? I guess I could rewrite this patch so it falls
 back to the gpg binary if gpgme is not available ...
 
 To install this patch on Debian/Ubuntu you can either
 
 * apt-get install libgpgme-ruby
 * apt-get install libgpgme11-dev; gem install gpgme
 
 Hamish Downer
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-Converted-crypto-to-use-the-gpgme-gem.patch
 Type: text/x-patch
 Size: 13168 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101106/69fefdfe/attachment-0001.bin>
 
 From dmishd@gmail.com  Mon Nov  8 06:21:12 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Mon, 8 Nov 2010 11:21:12 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 Message-ID: <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 
 Best hang fire on this patch. It appears to crash when verifying a signature
 when the public key is not available. I'm investigating the problem and how
 to fix it cleanly and I'll resubmit once I've done that.
 
 Hamish
 
 On Nov 6, 2010 8:08 PM, "Hamish D" <dmishd at gmail.com> wrote:
 
 I often find that loading long threads of encrypted messages (I have
 several of over 10 messages and one of nearly 40) leads to lots of
 flickering as the console replaces sup, sup comes back, the console
 comes back again ... It is also very slow, and involves writing
 decrypted messages to disk (if only temporarily) which could be a
 security hole. So I've looked about and found the gpgme gem which
 provides an API to use, and allows decryption entirely in memory.
 
 So I've rewritten lib/sup/crypto.rb to use gpgme. The functionality is
 pretty much the same. Things I'm aware of that are different:
 
 * we can't set the signature algorithm, so we have to use whatever is
 set in the user's preferences
 * the gpg-args hook has been replaced by the gpg-options hook
 
 Other than that I think it is the same, although it took some work to
 get the signature output to be the same. The other main difference is
 that it's much faster and nicer now :)
 
 It could do with some testing - I don't have much in the way of
 messages that cause gpg to complain, so if you do, please try opening
 those messages with this code and see if the behaviour is reasonable -
 no crashes, given messages about why your message was bad etc.
 
 Also I guess I should ask if people are happy to use this gem. Is it
 hard to use on Macs? I guess I could rewrite this patch so it falls
 back to the gpg binary if gpgme is not available ...
 
 To install this patch on Debian/Ubuntu you can either
 
 * apt-get install libgpgme-ruby
 * apt-get install libgpgme11-dev; gem install gpgme
 
 Hamish Downer
 -------------- next part --------------
 An HTML attachment was scrubbed...
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101108/e614209c/attachment.html>
 
 From dmishd@gmail.com  Mon Nov  8 17:32:15 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Mon, 8 Nov 2010 22:32:15 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 Message-ID: <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 
 OK, the second patch fixes the problem with the first patch.
 
 Hamish Downer
 
 On 8 November 2010 11:21, Hamish D <dmishd at gmail.com> wrote:
 > Best hang fire on this patch. It appears to crash when verifying a signature
 > when the public key is not available. I'm investigating the problem and how
 > to fix it cleanly and I'll resubmit once I've done that.
 >
 > Hamish
 >
 > On Nov 6, 2010 8:08 PM, "Hamish D" <dmishd at gmail.com> wrote:
 >
 > I often find that loading long threads of encrypted messages (I have
 > several of over 10 messages and one of nearly 40) leads to lots of
 > flickering as the console replaces sup, sup comes back, the console
 > comes back again ... It is also very slow, and involves writing
 > decrypted messages to disk (if only temporarily) which could be a
 > security hole. So I've looked about and found the gpgme gem which
 > provides an API to use, and allows decryption entirely in memory.
 >
 > So I've rewritten lib/sup/crypto.rb to use gpgme. The functionality is
 > pretty much the same. Things I'm aware of that are different:
 >
 > * we can't set the signature algorithm, so we have to use whatever is
 > set in the user's preferences
 > * the gpg-args hook has been replaced by the gpg-options hook
 >
 > Other than that I think it is the same, although it took some work to
 > get the signature output to be the same. The other main difference is
 > that it's much faster and nicer now :)
 >
 > It could do with some testing - I don't have much in the way of
 > messages that cause gpg to complain, so if you do, please try opening
 > those messages with this code and see if the behaviour is reasonable -
 > no crashes, given messages about why your message was bad etc.
 >
 > Also I guess I should ask if people are happy to use this gem. Is it
 > hard to use on Macs? I guess I could rewrite this patch so it falls
 > back to the gpg binary if gpgme is not available ...
 >
 > To install this patch on Debian/Ubuntu you can either
 >
 > * apt-get install libgpgme-ruby
 > * apt-get install libgpgme11-dev; gem install gpgme
 >
 > Hamish Downer
 >
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-Converted-crypto-to-use-the-gpgme-gem.patch
 Type: text/x-patch
 Size: 13172 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101108/7f25d4e2/attachment-0002.bin>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0002-catch-exception-when-no-public-key-present.patch
 Type: text/x-patch
 Size: 1571 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101108/7f25d4e2/attachment-0003.bin>
 
 From eg@gaute.vetsj.com  Tue Nov  9 05:19:47 2010
 From: eg@gaute.vetsj.com (Gaute Hope)
 Date: Tue, 09 Nov 2010 11:19:47 +0100
 Subject: [sup-devel] [PATCHES] more utf + whitespace
 Message-ID: <1289297820-sup-9801@qwerzila>
 
 Hi,
 
 attached is another patch fixing a crash first tab completing an UTF-8
 contact; then an ASCII contact.
 
 Also some whitespace corrections for lib/sup/buffer.rb
 
 Also available on:
 http://git.gitorious.org/~gauteh/sup/gautehs-mainline.git (master)
 
 
 - gaute
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-Fix-Whitespace-errors-in-buffer.rb.patch
 Type: application/octet-stream
 Size: 2393 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101109/bfddf0a1/attachment.obj>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0002-UTF-8-Force-UTF-8-in-ask_many_emails.patch
 Type: application/octet-stream
 Size: 1199 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101109/bfddf0a1/attachment-0001.obj>
 
 From sup-bugs@masanjin.net  Tue Nov  9 09:29:25 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Tue, 09 Nov 2010 14:29:25 +0000
 Subject: [sup-devel] [issue127] crash on searchin for "on:yesterday"
 In-Reply-To: <1289312965.5.0.992137177273.issue127@masanjin.net>
 Message-ID: <1289312965.5.0.992137177273.issue127@masanjin.net>
 
 
 New submission from anonymous:
 
 Hi,
 
 I've been reading the NewUserGuide.txt and did a search with \. At first, the
 status bar was like this:
 [search-results-mode] search: "on:yesterday"   line 0 of 0
 After quite some minutes of really high CPU load, it was like this:
 [Tue Nov 09 15:18:06 +0100 2010] ERROR: oh crap, an exception
 
 I've attached the the exception log of the exception as an attachment.
 
 Cu.
 
 ----------
 files: exception-log.txt
 messages: 301
 nosy: anonymous
 priority: bug
 ruby_version: 1.8.7
 status: unread
 sup_version: 0.11
 title: crash on searchin for "on:yesterday"
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue127>
 _________________________________________
 -------------- next part --------------
 --- NoMethodError from thread: periodic poll
 undefined method `content_width' for nil:NilClass
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:920:in `from_width'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:840:in `text_for_thread_at'
 /usr/lib/ruby/1.8/sup/index.rb:487:in `each_with_index'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:839:in `each'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:839:in `each_with_index'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:839:in `text_for_thread_at'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:781:in `regen_text'
 /usr/lib/ruby/1.8/sup/util.rb:414:in `map_with_index'
 /usr/lib/ruby/1.8/sup/index.rb:487:in `each_with_index'
 /usr/lib/ruby/1.8/sup/util.rb:414:in `each'
 /usr/lib/ruby/1.8/sup/util.rb:414:in `each_with_index'
 /usr/lib/ruby/1.8/sup/util.rb:414:in `map_with_index'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:781:in `regen_text'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:242:in `update'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:717:in `add_or_unhide'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:196:in `handle_added_update'
 /usr/lib/ruby/1.8/sup/update.rb:26:in `send'
 /usr/lib/ruby/1.8/sup/update.rb:26:in `relay'
 /usr/lib/ruby/1.8/sup/update.rb:26:in `each'
 /usr/lib/ruby/1.8/sup/update.rb:26:in `relay'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:191:in `add_new_message'
 /usr/lib/ruby/1.8/sup/poll.rb:132:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:176:in `each_message_from'
 /usr/lib/ruby/1.8/sup/maildir.rb:160:in `each'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `upto'
 /usr/lib/ruby/1.8/sup/maildir.rb:157:in `each'
 /usr/lib/ruby/1.8/sup/util.rb:610:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:610:in `__pass'
 /usr/lib/ruby/1.8/sup/util.rb:597:in `method_missing'
 /usr/lib/ruby/1.8/sup/poll.rb:164:in `each_message_from'
 /usr/lib/ruby/1.8/sup/poll.rb:116:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:104:in `each'
 /usr/lib/ruby/1.8/sup/poll.rb:104:in `do_poll'
 /usr/lib/ruby/1.8/sup/poll.rb:103:in `synchronize'
 /usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
 /usr/lib/ruby/1.8/sup/poll.rb:50:in `poll_with_sources'
 /usr/lib/ruby/1.8/sup/poll.rb:69:in `poll'
 /usr/lib/ruby/1.8/sup/poll.rb:87:in `start'
 /usr/lib/ruby/1.8/sup.rb:75:in `reporting_thread'
 /usr/lib/ruby/1.8/sup.rb:73:in `initialize'
 /usr/lib/ruby/1.8/sup.rb:73:in `new'
 /usr/lib/ruby/1.8/sup.rb:73:in `reporting_thread'
 /usr/lib/ruby/1.8/sup/poll.rb:84:in `start'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `send'
 /usr/lib/ruby/1.8/sup/util.rb:570:in `method_missing'
 /usr/bin/sup-mail:239
 
 From alvherre@alvh.no-ip.org  Tue Nov  9 10:22:39 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Tue, 09 Nov 2010 12:22:39 -0300
 Subject: [sup-devel] Fix crash on attachment with / in the name
 Message-ID: <1289316052-sup-7690@alvh.no-ip.org>
 
 This patch fixes an exception when the attachment specifies a filename
 with slashes.  This is rare but possible.
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-Fix-crash-on-handling-attachment-filenames-with.patch
 Type: application/octet-stream
 Size: 764 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101109/aef235de/attachment.obj>
 
 From alvherre@alvh.no-ip.org  Tue Nov  9 10:24:13 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Tue, 09 Nov 2010 12:24:13 -0300
 Subject: [sup-devel] Use "-- " as a signature separator
 Message-ID: <1289316177-sup-6046@alvh.no-ip.org>
 
 This patch makes the signature separator always be dash-dash-space; the
 current code is inconsistent in that one place is missing the space.
 Apparently, it was removed by someone who thought it was unnecessary.
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0002-Use-for-signature-separator.patch
 Type: application/octet-stream
 Size: 797 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101109/dc51b54c/attachment.obj>
 
 From alvherre@alvh.no-ip.org  Tue Nov  9 10:27:06 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Tue, 09 Nov 2010 12:27:06 -0300
 Subject: [sup-devel] pass //IGNORE to iconv
 Message-ID: <1289316270-sup-7500@alvh.no-ip.org>
 
 
 With the current code, an encoding failure means we see (and quote)
 stuff like \xab\xbc\x07 in the text.  Using the //IGNORE flag allows the
 code to ignore broken chars instead of displaying large amounts of junk.
 
 I note that the text containing broken chars is coming from external
 sources, so there's nothing that could be done locally to fix it.
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0003-Make-encoding-conversion-pass-IGNORE-to-iconv.patch
 Type: application/octet-stream
 Size: 1609 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101109/4ae5566b/attachment.obj>
 
 From chris.mason@ORACLE.COM  Tue Nov  9 19:40:58 2010
 From: chris.mason@ORACLE.COM (Chris Mason)
 Date: Tue, 09 Nov 2010 19:40:58 -0500
 Subject: [sup-devel] really high wakeup count in powertop
 Message-ID: <1289349454-sup-1015@think>
 
 Hi everyone,
 
 I'm new to sup and really like the interface and the features.  But, I
 popped up powertop while it was running and sup accounts for a constant 100
 wakeups/second, much more than the one or two wakeups/sec from our old
 friend mutt.
 
 I haven't done much ruby but can make my way through most things.  If
 someone could point me at the polling function most likely to cause the
 wakeups I can work out a patch.
 
 I'm running git from this Monday, so pretty recent.  Ruby 1.9.1
 
 Thanks!
 
 -chris
 
 From chris.mason@oracle.com  Wed Nov 10 09:41:30 2010
 From: chris.mason@oracle.com (Chris Mason)
 Date: Wed, 10 Nov 2010 09:41:30 -0500
 Subject: [sup-devel] really high wakeup count in powertop
 In-Reply-To: <1289349454-sup-1015@think>
 References: <1289349454-sup-1015@think>
 Message-ID: <1289399902-sup-201@think>
 
 Excerpts from Chris Mason's message of 2010-11-09 19:40:58 -0500:
 > Hi everyone,
 > 
 > I'm new to sup and really like the interface and the features.  But, I
 > popped up powertop while it was running and sup accounts for a constant 100
 > wakeups/second, much more than the one or two wakeups/sec from our old
 > friend mutt.
 > 
 > I haven't done much ruby but can make my way through most things.  If
 > someone could point me at the polling function most likely to cause the
 > wakeups I can work out a patch.
 > 
 > I'm running git from this Monday, so pretty recent.  Ruby 1.9.1
 
 (This got dumped into the moderator approval queue, so I'm resending,
 this time with more details)
 
 strace showed we were hammering on futexes, and a little digging made it
 clear sup isn't to blame.  The ruby timer thread is polling for
 signals (or something) every 10ms:
 
 http://redmine.ruby-lang.org/issues/show/3436
 
 I patched up ruby to poll every 500ms and things seem to work.  Not sure
 why the ruby developers didn't just change the timeout, but chances are
 good they have a real reason.  I'll post to that bug.
 
 -chris
 
 From eg@gaute.vetsj.com  Wed Nov 10 11:13:48 2010
 From: eg@gaute.vetsj.com (Gaute Hope)
 Date: Wed, 10 Nov 2010 17:13:48 +0100
 Subject: [sup-devel] really high wakeup count in powertop
 In-Reply-To: <1289399902-sup-201@think>
 References: <1289349454-sup-1015@think> <1289399902-sup-201@think>
 Message-ID: <1289405570-sup-2035@qwerzila>
 
 Excerpts from Chris Mason's message of 2010-11-10 15:41:30 +0100:
 > strace showed we were hammering on futexes, and a little digging made it
 > clear sup isn't to blame.  The ruby timer thread is polling for
 > signals (or something) every 10ms:
 > 
 > http://redmine.ruby-lang.org/issues/show/3436
 > 
 > I patched up ruby to poll every 500ms and things seem to work.  Not sure
 > why the ruby developers didn't just change the timeout, but chances are
 > good they have a real reason.  I'll post to that bug.
 
 Also noticed sup in powertop; so there's nothing to do on the Sup side ?
 
 - gaute
 
 From wmorgan-sup@masanjin.net  Wed Nov 10 13:35:41 2010
 From: wmorgan-sup@masanjin.net (William Morgan)
 Date: Wed, 10 Nov 2010 13:35:41 -0500
 Subject: [sup-devel] really high wakeup count in powertop
 In-Reply-To: <1289399902-sup-201@think>
 References: <1289349454-sup-1015@think> <1289399902-sup-201@think>
 Message-ID: <1289414078-sup-6701@masanjin.net>
 
 Reformatted excerpts from Chris Mason's message of 2010-11-10:
 > I patched up ruby to poll every 500ms and things seem to work.  Not
 > sure why the ruby developers didn't just change the timeout, but
 > chances are good they have a real reason.
 
 Yeah, the last time someone investigated this, they decided it was a
 Ruby issue as well. Keep us informed if that patch gets applied. You
 could also try 1.9.2 for kicks.
 -- 
 William <wmorgan-sup at masanjin.net>
 
 From chris.mason@oracle.com  Wed Nov 10 15:18:58 2010
 From: chris.mason@oracle.com (Chris Mason)
 Date: Wed, 10 Nov 2010 15:18:58 -0500
 Subject: [sup-devel] really high wakeup count in powertop
 In-Reply-To: <1289414078-sup-6701@masanjin.net>
 References: <1289349454-sup-1015@think> <1289399902-sup-201@think>
 	<1289414078-sup-6701@masanjin.net>
 Message-ID: <1289420219-sup-8511@think>
 
 Excerpts from William Morgan's message of 2010-11-10 13:35:41 -0500:
 > Reformatted excerpts from Chris Mason's message of 2010-11-10:
 > > I patched up ruby to poll every 500ms and things seem to work.  Not
 > > sure why the ruby developers didn't just change the timeout, but
 > > chances are good they have a real reason.
 > 
 > Yeah, the last time someone investigated this, they decided it was a
 > Ruby issue as well. Keep us informed if that patch gets applied. You
 > could also try 1.9.2 for kicks.
 
 The 500ms patch apparently isn't good because it limits how often ruby
 can switch between threads.  This seems strange to me, because the
 kernel should be scheduling the threads, so I'll ask again.
 
 At any rate, it did trigger some discussion and doesn't seem to be fixed
 yet in any ruby version.
 
 (For sup uses, 500ms works just fine, and that's my only ruby app).
 
 -chris
 
 From gaudenz@soziologie.ch  Thu Nov 11 04:09:18 2010
 From: gaudenz@soziologie.ch (Gaudenz Steinlin)
 Date: Thu, 11 Nov 2010 10:09:18 +0100
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 Message-ID: <1289466286-sup-7540@meteor.durcheinandertal.local>
 
 Hi
 
 Excerpts from Hamish D's message of Mon Nov 08 23:32:15 +0100 2010:
 > OK, the second patch fixes the problem with the first patch.
 
 I tried your patches and the problem with crash on missing keys seems
 to be solved. However I have some more comments:
 
 - With this patch the output of the gpg run is no longer available.
   Like this the plus sign in front of the message does not make sense.
   Is there a way to get at the gpg output with your approach?
 - Signatures made by keys that are available in my keyring but aren't
   trusted are shown as valid. They should be specially marked!
   This is not a new problem. It also exists with the current code, but
   there you can access the gpg output which shows you that the
   signature is valid but not trusted.
 
 Gaudenz
 
 > 
 > Hamish Downer
 > 
 > On 8 November 2010 11:21, Hamish D <dmishd at gmail.com> wrote:
 > > Best hang fire on this patch. It appears to crash when verifying a signature
 > > when the public key is not available. I'm investigating the problem and how
 > > to fix it cleanly and I'll resubmit once I've done that.
 > >
 > > Hamish
 > >
 > > On Nov 6, 2010 8:08 PM, "Hamish D" <dmishd at gmail.com> wrote:
 > >
 > > I often find that loading long threads of encrypted messages (I have
 > > several of over 10 messages and one of nearly 40) leads to lots of
 > > flickering as the console replaces sup, sup comes back, the console
 > > comes back again ... It is also very slow, and involves writing
 > > decrypted messages to disk (if only temporarily) which could be a
 > > security hole. So I've looked about and found the gpgme gem which
 > > provides an API to use, and allows decryption entirely in memory.
 > >
 > > So I've rewritten lib/sup/crypto.rb to use gpgme. The functionality is
 > > pretty much the same. Things I'm aware of that are different:
 > >
 > > * we can't set the signature algorithm, so we have to use whatever is
 > > set in the user's preferences
 > > * the gpg-args hook has been replaced by the gpg-options hook
 > >
 > > Other than that I think it is the same, although it took some work to
 > > get the signature output to be the same. The other main difference is
 > > that it's much faster and nicer now :)
 > >
 > > It could do with some testing - I don't have much in the way of
 > > messages that cause gpg to complain, so if you do, please try opening
 > > those messages with this code and see if the behaviour is reasonable -
 > > no crashes, given messages about why your message was bad etc.
 > >
 > > Also I guess I should ask if people are happy to use this gem. Is it
 > > hard to use on Macs? I guess I could rewrite this patch so it falls
 > > back to the gpg binary if gpgme is not available ...
 > >
 > > To install this patch on Debian/Ubuntu you can either
 > >
 > > * apt-get install libgpgme-ruby
 > > * apt-get install libgpgme11-dev; gem install gpgme
 > >
 > > Hamish Downer
 > >
 --
 Ever tried. Ever failed. No matter.
 Try again. Fail again. Fail better.
 ~ Samuel Beckett ~
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 482 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101111/0cb505ea/attachment.bin>
 
 From dmishd@gmail.com  Thu Nov 11 12:25:13 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Thu, 11 Nov 2010 17:25:13 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <1289466286-sup-7540@meteor.durcheinandertal.local>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 Message-ID: <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 
 > - With this patch the output of the gpg run is no longer available.
 > ?Like this the plus sign in front of the message does not make sense.
 > ?Is there a way to get at the gpg output with your approach?
 
 The gpg binary is not called, so there is no output from it. What do
 you mean by the "plus sign" - where does this turn up? I haven't
 noticed that. If you tell me exactly what your expected behaviour is
 I'll see if I can replicate it.
 
 > - Signatures made by keys that are available in my keyring but aren't
 > ?trusted are shown as valid. They should be specially marked!
 > ?This is not a new problem. It also exists with the current code, but
 > ?there you can access the gpg output which shows you that the
 > ?signature is valid but not trusted.
 
 I have a hook I'm working on so that you can access the full Signature
 object returned by gpgme. I'll post about it when it's working and I
 have some example hook code. This would be able to tell you whether
 the key that signed the message is trusted by you etc. I'll hopefully
 get to that within a week.
 
 Hamish
 
 From sup-bugs@masanjin.net  Sat Nov 13 05:49:52 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Sat, 13 Nov 2010 10:49:52 +0000
 Subject: [sup-devel] [issue128] can't modify frozen string
 In-Reply-To: <1289645392.0.0.856118231746.issue128@masanjin.net>
 Message-ID: <1289645392.0.0.856118231746.issue128@masanjin.net>
 
 
 New submission from anonymous:
 
 see the exception log..
 
 ----------
 messages: 302
 nosy: anonymous
 priority: bug
 ruby_version: 1.9.1
 status: unread
 sup_version: 0.11
 title: can't modify frozen string
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue128>
 _________________________________________
 
 From rlane@club.cc.cmu.edu  Sun Nov 14 23:16:35 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Sun, 14 Nov 2010 23:16:35 -0500
 Subject: [sup-devel] [PATCHES] more utf + whitespace
 In-Reply-To: <1289297820-sup-9801@qwerzila>
 References: <1289297820-sup-9801@qwerzila>
 Message-ID: <1289794572-sup-2762@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Sun Nov 14 23:17:03 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Sun, 14 Nov 2010 23:17:03 -0500
 Subject: [sup-devel] Fix crash on attachment with / in the name
 In-Reply-To: <1289316052-sup-7690@alvh.no-ip.org>
 References: <1289316052-sup-7690@alvh.no-ip.org>
 Message-ID: <1289794607-sup-2409@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Sun Nov 14 23:17:31 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Sun, 14 Nov 2010 23:17:31 -0500
 Subject: [sup-devel] Use "-- " as a signature separator
 In-Reply-To: <1289316177-sup-6046@alvh.no-ip.org>
 References: <1289316177-sup-6046@alvh.no-ip.org>
 Message-ID: <1289794629-sup-8400@zyrg.net>
 
 Applied to master.
 
 From rlane@club.cc.cmu.edu  Sun Nov 14 23:17:59 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Sun, 14 Nov 2010 23:17:59 -0500
 Subject: [sup-devel] pass //IGNORE to iconv
 In-Reply-To: <1289316270-sup-7500@alvh.no-ip.org>
 References: <1289316270-sup-7500@alvh.no-ip.org>
 Message-ID: <1289794660-sup-7534@zyrg.net>
 
 Applied to master.
 
 From sup-bugs@masanjin.net  Mon Nov 15 03:40:11 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Mon, 15 Nov 2010 08:40:11 +0000
 Subject: [sup-devel] [issue129] error while trying to reply to a message
 	with CC and gpg	sign
 In-Reply-To: <1289810410.96.0.779211820573.issue129@masanjin.net>
 Message-ID: <1289810410.96.0.779211820573.issue129@masanjin.net>
 
 
 New submission from anonymous:
 
 I can't reply to a conversation signing with gpg, if the email has some cc
 
 ----------
 files: exception-log.txt
 messages: 303
 nosy: anonymous
 priority: bug
 ruby_version: 1.9.1
 status: unread
 sup_version: 0.11
 title: error while trying to reply to a message with CC and gpg sign
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue129>
 _________________________________________
 -------------- next part --------------
 --- Redwood::FatalSourceError from thread: main
 While communicating with IMAP server (type Net::IMAP::BadResponseError): "Could not parse command"
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/imap.rb:343:in `rescue in safely'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/imap.rb:329:in `safely'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/imap.rb:121:in `store_message'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/util.rb:610:in `__pass'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/util.rb:597:in `method_missing'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/sent.rb:28:in `write_sent_message'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/modes/edit-message-mode.rb:346:in `send_message'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/mode.rb:59:in `handle_input'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/buffer.rb:279:in `handle_input'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/bin/sup:279:in `<module:Redwood>'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/bin/sup:68:in `<top (required)>'
 /usr/bin/sup:19:in `load'
 /usr/bin/sup:19:in `<main>'
 
 From chris.mason@oracle.com  Mon Nov 15 07:21:57 2010
 From: chris.mason@oracle.com (Chris Mason)
 Date: Mon, 15 Nov 2010 07:21:57 -0500
 Subject: [sup-devel] searching by message instead of thread
 Message-ID: <1289823372-sup-3394@think>
 
 Hi everyone,
 
 The default search setup in sup seems to just pop up the whole thread in
 the results, which helps a lot because you can easily find the
 related context.
 
 But, I often get stuck on threads that last for weeks and have many many
 messages.  It's hard to find the actual messages that match the search.
 
 Three things would help:
 
 1) Toggle between the whole thread and the matching messages in the
 thread view
 2) Expand just the matching messages and collapse the others
 3) When you hit / to search for text in the thread display, have a key
 for next.
 
 Do any of these already exist?  If not, which ones seem most likely to
 be acceptable?
 
 -chris
 
 From ali@lown.me.uk  Mon Nov 15 14:29:22 2010
 From: ali@lown.me.uk (Ali Lown)
 Date: Mon, 15 Nov 2010 19:29:22 +0000
 Subject: [sup-devel] state of maildir-sync branch?
 Message-ID: <1289849196-sup-128@alipc-laptop>
 
 What happened to this branch, because it hasn't been worked on since July, but doesn't appear to have been merged into master/next.
 Does anyone know what else needs to be done to get it suitable for merging (besides a git rebase)?
 -Ali
 
 
 From rlane@club.cc.cmu.edu  Mon Nov 15 15:52:59 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Mon, 15 Nov 2010 15:52:59 -0500
 Subject: [sup-devel] state of maildir-sync branch?
 In-Reply-To: <1289849196-sup-128@alipc-laptop>
 References: <1289849196-sup-128@alipc-laptop>
 Message-ID: <1289854240-sup-7909@zyrg.net>
 
 Excerpts from Ali Lown's message of Mon Nov 15 14:29:22 -0500 2010:
 > What happened to this branch, because it hasn't been worked on since July, but doesn't appear to have been merged into master/next.
 > Does anyone know what else needs to be done to get it suitable for merging (besides a git rebase)?
 > -Ali
 
 I'll take a look.
 
 From gaudenz@soziologie.ch  Tue Nov 16 06:42:33 2010
 From: gaudenz@soziologie.ch (Gaudenz Steinlin)
 Date: Tue, 16 Nov 2010 12:42:33 +0100
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 Message-ID: <1289907535-sup-3989@meteor.durcheinandertal.local>
 
 Excerpts from Hamish D's message of Don Nov 11 18:25:13 +0100 2010:
 > > - With this patch the output of the gpg run is no longer available.
 > > ?Like this the plus sign in front of the message does not make sense.
 > > ?Is there a way to get at the gpg output with your approach?
 > 
 > The gpg binary is not called, so there is no output from it. What do
 > you mean by the "plus sign" - where does this turn up? I haven't
 > noticed that. If you tell me exactly what your expected behaviour is
 > I'll see if I can replicate it.
 
 The "+" character is right in front of the string "Good signature from
 ...". If you move the cursor to that line and press enter it changes
 to a "-" character, but no additional text is shown. The gpg command
 output used to show up there when pressing enter. 
 
 I expect there to be some additional output about the signature
 validation like keyid, signature date, trust level, ... 
 
 At least if you can't provide any additional information, the "+"
 character should not show up as this is an indicator that there is
 some collapsed text to show.
 
 Gaudenz
 --
 Ever tried. Ever failed. No matter.
 Try again. Fail again. Fail better.
 ~ Samuel Beckett ~
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 482 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101116/17b84df7/attachment.bin>
 
 From dmishd@gmail.com  Tue Nov 16 09:20:03 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Tue, 16 Nov 2010 14:20:03 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <1289907535-sup-3989@meteor.durcheinandertal.local>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 Message-ID: <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 
 > The "+" character is right in front of the string "Good signature from
 > ...". If you move the cursor to that line and press enter it changes
 > to a "-" character, but no additional text is shown. The gpg command
 > output used to show up there when pressing enter.
 >
 > I expect there to be some additional output about the signature
 > validation like keyid, signature date, trust level, ...
 
 Right, now I know what you are referring to. It is a CryptoNotice
 object. That didn't work in the first version of the patch, but I
 fixed it in the patch I submitted the second time.
 
 So with the patches submitted in the message with time stamp "8
 November 2010 22:32"?there will be lines when you expand, telling you
 the key ID, the timestamp of the signature and all names and email
 addresses associated with that key.
 
 I am also working on having extra information generated when the key
 is not trusted, but this is not done yet. And I am also working on a
 hook where you can generate as much information as you want from the
 signature for the CryptoNotice. Hopefully be ready to submit before
 the weekend.
 
 While doing this I'm wondering about the preferred way of submitting
 patches that represent quite a bit of work. Should I use git rebase -i
 to just have a single patch with all changes, or is it preferred to
 have a series of smaller changes?
 
 I also have my code at http://github.com/foobacca/sup - this patch is
 being developed in the gpgme branch -
 https://github.com/foobacca/sup/tree/gpgme
 
 Hamish
 
 From damien.leone@fensalir.fr  Tue Nov 16 09:30:14 2010
 From: damien.leone@fensalir.fr (Damien Leone)
 Date: Tue, 16 Nov 2010 15:30:14 +0100
 Subject: [sup-devel] state of maildir-sync branch?
 In-Reply-To: <1289849196-sup-128@alipc-laptop>
 References: <1289849196-sup-128@alipc-laptop>
 Message-ID: <1289917099-sup-3698@mailer>
 
 Hello,
 
 I would say that the work is almost done, I still have things on my
 todo list which are:
 
 - Merge the replied/forwarded tag at the first synchronisation back to
   the IMAP so no information is lost
 
 - There is still some work to do on the Polling#do_poll function
   because the way it is in the branch is too hackish
 
 - Allow to move an email from a maildir to another
 
 - Put a special flag or file for the first time you run sup with the
   branch so you get asked if you want to sync everything now
 
 Beside that I have been running the branch for months without issue,
 just a little bug that might be related to the point 2 of the list.
 
 I often rebase the branch to master so it stays up to date, you can
 find this on my repository [0] in the maildir-sync-master branch. The
 damien branch is the same with extra patches I made months ago that
 have not been reviewed.
 
 Cheers,
 
 [0] : http://git.fensalir.fr/?p=dleone/sup.git;a=summary
 
 Excerpts from Ali Lown's message of lun. nov. 15 20:29:22 +0100 2010:
 > What happened to this branch, because it hasn't been worked on since July, but doesn't appear to have been merged into master/next.
 > Does anyone know what else needs to be done to get it suitable for merging (besides a git rebase)?
 
 -- 
 Damien Leone <damien.leone at fensalir.fr>
 
 Web: http://dleone.fensalir.fr/
 GPG: 0x82EB4DDF
 
 From alvherre@alvh.no-ip.org  Tue Nov 16 10:35:32 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Tue, 16 Nov 2010 12:35:32 -0300
 Subject: [sup-devel] state of maildir-sync branch?
 In-Reply-To: <1289917099-sup-3698@mailer>
 References: <1289849196-sup-128@alipc-laptop> <1289917099-sup-3698@mailer>
 Message-ID: <1289921639-sup-8166@alvh.no-ip.org>
 
 Excerpts from Damien Leone's message of mar nov 16 11:30:14 -0300 2010:
 
 > - Allow to move an email from a maildir to another
 
 Somewhat related: I'd like to have a display of which source(s) a
 message belongs to, in the header widget.  I have no idea how to
 implement this though.  Any pointers?
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 
 From gaudenz@soziologie.ch  Tue Nov 16 13:36:55 2010
 From: gaudenz@soziologie.ch (Gaudenz Steinlin)
 Date: Tue, 16 Nov 2010 19:36:55 +0100
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 	<AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 Message-ID: <1289932061-sup-96@meteor.durcheinandertal.local>
 
 Excerpts from Hamish D's message of Die Nov 16 15:20:03 +0100 2010:
 > > The "+" character is right in front of the string "Good signature from
 > > ...". If you move the cursor to that line and press enter it changes
 > > to a "-" character, but no additional text is shown. The gpg command
 > > output used to show up there when pressing enter.
 > >
 > > I expect there to be some additional output about the signature
 > > validation like keyid, signature date, trust level, ...
 > 
 > Right, now I know what you are referring to. It is a CryptoNotice
 > object. That didn't work in the first version of the patch, but I
 > fixed it in the patch I submitted the second time.
 > 
 > So with the patches submitted in the message with time stamp "8
 > November 2010 22:32"?there will be lines when you expand, telling you
 > the key ID, the timestamp of the signature and all names and email
 > addresses associated with that key.
 
 This does not work for me when running the foobacca/gpgme tree (commit
 7b9a1eeeaaa25931963e2de49410d7cb0c7e6772). The CryptoNotice is empty.
 I'm using the following packages from Debians testing distribution:
 - ruby1.8 1.8.7.302-2
 - libgpgme-ruby1.8 1.0.8-3
 - libgpgme11 1.2.0-1.2
 - libgpg-error0 1.6-1
 
 Please tell me if you need further information to debug the problem.
 
 > 
 > I am also working on having extra information generated when the key
 > is not trusted, but this is not done yet. And I am also working on a
 > hook where you can generate as much information as you want from the
 > signature for the CryptoNotice. Hopefully be ready to submit before
 > the weekend.
 
 This sounds nice. Thanks for your work!
 
 > 
 > While doing this I'm wondering about the preferred way of submitting
 > patches that represent quite a bit of work. Should I use git rebase -i
 > to just have a single patch with all changes, or is it preferred to
 > have a series of smaller changes?
 
 Dunno about the official policy. I'd say break it if the pieces are
 usefull on their own (but may depend on each other), otherwise make
 them one patch.
 
 Gaudenz
 --
 Ever tried. Ever failed. No matter.
 Try again. Fail again. Fail better.
 ~ Samuel Beckett ~
 
 From dmishd@gmail.com  Tue Nov 16 18:05:50 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Tue, 16 Nov 2010 23:05:50 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <1289932061-sup-96@meteor.durcheinandertal.local>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 	<AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 	<1289932061-sup-96@meteor.durcheinandertal.local>
 Message-ID: <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
 
 > This does not work for me when running the foobacca/gpgme tree (commit
 > 7b9a1eeeaaa25931963e2de49410d7cb0c7e6772). The CryptoNotice is empty.
 
 Oops. I had one too many flatten! calls and was using the
 output_lines.flatten! as a return value. However flatten! returns nil
 if there is no flattening to be done. I've now fixed this in the
 github tree. Please try it out and let me know how it works for you.
 
 >> I am also working on having extra information generated when the key
 >> is not trusted, but this is not done yet. And I am also working on a
 >> hook where you can generate as much information as you want from the
 >> signature for the CryptoNotice. Hopefully be ready to submit before
 >> the weekend.
 >
 > This sounds nice. Thanks for your work!
 
 And thank you for your testing and patience :)
 
 The github version also has the sig-output hook set up. From the hook text:
 
 START
 Runs when the signature output is being generated, allowing you to
 add extra information to your signatures if you want.
 
 Variables:
 signature: the signature object (class is GPGME::Signature)
 from_key: the key that generated the signature (class is GPGME::Key)
 
 Return value: an array of lines of output
 END
 
 I've attached a sample hook file if you want to have a play with it.
 I'll document this all on the wiki if it gets accepted.
 
 I'll give you a few days to find some more problems, but if you fail
 to find any then I'll package this up as a single patch and resubmit
 it all.
 
 Hamish
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: sig-output.rb
 Type: application/x-ruby
 Size: 1221 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101116/364d19ee/attachment-0001.bin>
 
 From cam+sup@cammunism.org  Tue Nov 16 18:25:47 2010
 From: cam+sup@cammunism.org (Cameron Matheson)
 Date: Tue, 16 Nov 2010 16:25:47 -0700
 Subject: [sup-devel] searching by message instead of thread
 In-Reply-To: <1289823372-sup-3394@think>
 References: <1289823372-sup-3394@think>
 Message-ID: <1289949866-sup-2187@cammunism.org>
 
 Excerpts from Chris Mason's message of Mon Nov 15 05:21:57 -0700 2010:
 > 3) When you hit / to search for text in the thread display, have a key
 > for next.
 > 
 > Do any of these already exist?  If not, which ones seem most likely to
 > be acceptable?
 
 You can hit 'n' for the next match when searching.  (Not sure about the
 others)
 
 Cam
 
 From sup-bugs@masanjin.net  Wed Nov 17 16:49:11 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Wed, 17 Nov 2010 21:49:11 +0000
 Subject: [sup-devel] [issue130] Use list of labels to add label
 In-Reply-To: <1290030551.54.0.220148230728.issue130@masanjin.net>
 Message-ID: <1290030551.54.0.220148230728.issue130@masanjin.net>
 
 
 New submission from anonymous:
 
 In thread viewing mode it is possible to search for labels using a last of all existing labels by pressing <L><enter>. It would help adding new labels and avoiding typing errors if such a list of existing labels was implemented for the <l> command for adding labels.
 
 ----------
 messages: 305
 nosy: anonymous
 priority: feature request
 ruby_version: 1.8
 status: unread
 sup_version: 0.10.2
 title: Use list of labels to add label
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue130>
 _________________________________________
 
 From damien.leone@fensalir.fr  Thu Nov 18 07:30:24 2010
 From: damien.leone@fensalir.fr (Damien Leone)
 Date: Thu, 18 Nov 2010 13:30:24 +0100
 Subject: [sup-devel] state of maildir-sync branch?
 In-Reply-To: <1289921639-sup-8166@alvh.no-ip.org>
 References: <1289849196-sup-128@alipc-laptop> <1289917099-sup-3698@mailer>
 	<1289921639-sup-8166@alvh.no-ip.org>
 Message-ID: <1290082837-sup-9842@mailer>
 
 Hi,
 
 Excerpts from Alvaro Herrera's message of mar. nov. 16 16:35:32 +0100 2010:
 > Somewhat related: I'd like to have a display of which source(s) a
 > message belongs to, in the header widget.  I have no idea how to
 > implement this though.  Any pointers?
 
 If I remember correctly you can retrieve the source informations of a
 mail by its "locations" attribute in the Message class.
 
 A Location is a class which has a "source" attribute that can be
 Maildir or Mbox and an "info" attribute that holds the filename on the
 disk.
 
 -- 
 Damien Leone <damien.leone at fensalir.fr>
 
 Web: http://dleone.fensalir.fr/
 GPG: 0x82EB4DDF
 
 From alvherre@alvh.no-ip.org  Thu Nov 18 09:50:48 2010
 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
 Date: Thu, 18 Nov 2010 11:50:48 -0300
 Subject: [sup-devel] state of maildir-sync branch?
 In-Reply-To: <1290082837-sup-9842@mailer>
 References: <1289849196-sup-128@alipc-laptop> <1289917099-sup-3698@mailer>
 	<1289921639-sup-8166@alvh.no-ip.org> <1290082837-sup-9842@mailer>
 Message-ID: <1290091834-sup-636@alvh.no-ip.org>
 
 Excerpts from Damien Leone's message of jue nov 18 09:30:24 -0300 2010:
 > Hi,
 > 
 > Excerpts from Alvaro Herrera's message of mar. nov. 16 16:35:32 +0100 2010:
 > > Somewhat related: I'd like to have a display of which source(s) a
 > > message belongs to, in the header widget.  I have no idea how to
 > > implement this though.  Any pointers?
 > 
 > If I remember correctly you can retrieve the source informations of a
 > mail by its "locations" attribute in the Message class.
 > 
 > A Location is a class which has a "source" attribute that can be
 > Maildir or Mbox and an "info" attribute that holds the filename on the
 > disk.
 
 Ah, great, thanks.
 
 -- 
 ?lvaro Herrera <alvherre at alvh.no-ip.org>
 
 From sup-bugs@masanjin.net  Sun Nov 21 11:55:08 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Sun, 21 Nov 2010 16:55:08 +0000
 Subject: [sup-devel] [issue131] Both 0.11 from Ubuntu and current git head
 	fail
 In-Reply-To: <1290358508.13.0.586728234645.issue131@masanjin.net>
 Message-ID: <1290358508.13.0.586728234645.issue131@masanjin.net>
 
 
 New submission from anonymous:
 
 I've been using Sup 0.11 on Ubuntu 10.10 from the distribution packages. I use a
 local Maildir and sync it with my remote IMAP account. I'm running with Unicode
 support using libncursesw5.
 
 Sup crashes from time to time and sometimes asks to run sup-sync (presumably
 because I move/delete messages in my remote mailbox).
 
 Unfortunately I'm not able to recover from today's crash. I tried checking out
 the current development head from git and running that with `ruby -I lib -w
 bin/sup` but it crashed as well.
 
 I'm attaching the exception logs from crashes of both versions.
 
 ----------
 files: sup-0.11-2-ubuntu-exception-log.txt
 messages: 306
 nosy: anonymous
 priority: bug
 ruby_version: 1.8
 status: unread
 sup_version: 0.11
 title: Both 0.11 from Ubuntu and current git head fail
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue131>
 _________________________________________
 -------------- next part --------------
 --- RuntimeError from thread: load threads for thread-index-mode
 
 /usr/lib/ruby/1.8/sup/index.rb:501:in `find_docid'
 /usr/lib/ruby/1.8/sup/index.rb:506:in `find_doc'
 /usr/lib/ruby/1.8/sup/index.rb:516:in `get_entry'
 /usr/lib/ruby/1.8/sup/index.rb:193:in `build_message'
 /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
 /usr/lib/ruby/1.8/sup/index.rb:525:in `synchronize'
 /usr/lib/ruby/1.8/sup/index.rb:193:in `build_message'
 /usr/lib/ruby/1.8/sup/index.rb:148:in `each_id_by_date'
 /usr/lib/ruby/1.8/sup/thread.rb:332:in `call'
 /usr/lib/ruby/1.8/sup/thread.rb:332:in `load_n_threads'
 /usr/lib/ruby/1.8/sup/index.rb:148:in `each_id_by_date'
 /usr/lib/ruby/1.8/sup/index.rb:239:in `each_id'
 /usr/lib/ruby/1.8/sup/index.rb:239:in `each'
 /usr/lib/ruby/1.8/sup/index.rb:239:in `each_id'
 /usr/lib/ruby/1.8/sup/index.rb:148:in `each_id_by_date'
 /usr/lib/ruby/1.8/sup/thread.rb:328:in `load_n_threads'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in `__unprotected_load_n_threads'
 (eval):12:in `load_n_threads'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:624:in `load_n_threads_background'
 /usr/lib/ruby/1.8/sup.rb:75:in `reporting_thread'
 /usr/lib/ruby/1.8/sup.rb:73:in `initialize'
 /usr/lib/ruby/1.8/sup.rb:73:in `new'
 /usr/lib/ruby/1.8/sup.rb:73:in `reporting_thread'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:623:in `load_n_threads_background'
 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:694:in `__unprotected_load_threads'
 (eval):12:in `load_threads'
 /usr/bin/sup-mail:230
 
 From sup-bugs@masanjin.net  Tue Nov 23 05:36:48 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Tue, 23 Nov 2010 10:36:48 +0000
 Subject: [sup-devel] [issue132] strange encoding error
 In-Reply-To: <1290508608.33.0.253409523291.issue132@masanjin.net>
 Message-ID: <1290508608.33.0.253409523291.issue132@masanjin.net>
 
 
 New submission from anonymous:
 
 this happens when i try to send an email...
 
 ----------------------------------------------------------------
 --- Encoding::CompatibilityError from thread: main
 incompatible character encodings: UTF-8 and ASCII-8BIT
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:112:in
 `serialize_low'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:99:in `block in
 serialize_low'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:155:in `block in
 each_part'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:154:in `each'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:154:in `each_part'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:96:in
 `serialize_low'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:63:in `serialize'
 /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:146:in `to_s'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/modes/edit-message-mode.rb:344:in
 `puts'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/modes/edit-message-mode.rb:344:in
 `block in send_message'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/modes/edit-message-mode.rb:344:in
 `popen'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/modes/edit-message-mode.rb:344:in
 `send_message'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/mode.rb:59:in `handle_input'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/lib/sup/buffer.rb:279:in `handle_input'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/bin/sup:279:in `<module:Redwood>'
 /usr/lib/ruby/gems/1.9.1/gems/sup-0.11/bin/sup:68:in `<top (required)>'
 /usr/bin/sup:19:in `load'
 /usr/bin/sup:19:in `<main>'
 
 ----------
 messages: 311
 nosy: anonymous
 priority: bug
 ruby_version: 1.9.1
 status: unread
 sup_version: 0.11
 title: strange encoding error
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue132>
 _________________________________________
 
 From sup-bugs@masanjin.net  Sat Nov 27 06:15:50 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Sat, 27 Nov 2010 11:15:50 +0000
 Subject: [sup-devel] [issue133] add support for the mh mailbox format
 In-Reply-To: <1290856550.06.0.787394879314.issue133@masanjin.net>
 Message-ID: <1290856550.06.0.787394879314.issue133@masanjin.net>
 
 
 New submission from anonymous:
 
 I've been using the mh format (via nmh) for years, and it would be fantastic if 
 sup could support it so people don't have to convert mailboxes to maildir or mbox 
 to be able to use sup.
 
 ----------
 messages: 312
 nosy: anonymous
 priority: feature request
 ruby_version: 1.8
 status: unread
 sup_version: 0.11
 title: add support for the mh mailbox format
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue133>
 _________________________________________
 
 From rlane@club.cc.cmu.edu  Sat Nov 27 20:19:30 2010
 From: rlane@club.cc.cmu.edu (Rich Lane)
 Date: Sat, 27 Nov 2010 20:19:30 -0500
 Subject: [sup-devel] preparing for sup 0.12 release
 Message-ID: <1290906846-sup-2867@zyrg.net>
 
 Let me know of any release-blocking bugs (regressions from 0.11) that
 should be fixed first. The only one I know of is the broken sup-sync
 progress bar.
 
 From dmishd@gmail.com  Sun Nov 28 17:51:43 2010
 From: dmishd@gmail.com (Hamish D)
 Date: Sun, 28 Nov 2010 22:51:43 +0000
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 	<AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 	<1289932061-sup-96@meteor.durcheinandertal.local>
 	<AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
 Message-ID: <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
 
 OK, here is a set of 4 patches that implement the change over to the
 gpgme library. There's quite a bit of work in there so I thought I'd
 leave it as a few patches, but I have done some tidying.
 
 I have some more ideas for improvements, but I'm happy that this
 reproduces the behaviour of using the gpg binary, and I find sup usage
 much smoother with this change.
 
 I'll leave it for others to decide whether to stick this in sup 0.12 -
 I guess it could be risky to stick it in without it being tested, but
 maybe it could be applied to the next tree, and then moved to main
 after 0.12 has been released.
 
 Hamish Downer
 
 >
 > >> I am also working on having extra information generated when the key
 > >> is not trusted, but this is not done yet. And I am also working on a
 > >> hook where you can generate as much information as you want from the
 > >> signature for the CryptoNotice. Hopefully be ready to submit before
 > >> the weekend.
 > >
 > > This sounds nice. Thanks for your work!
 >
 > And thank you for your testing and patience :)
 >
 > The github version also has the sig-output hook set up. From the hook text:
 >
 > START
 > Runs when the signature output is being generated, allowing you to
 > add extra information to your signatures if you want.
 >
 > Variables:
 > signature: the signature object (class is GPGME::Signature)
 > from_key: the key that generated the signature (class is GPGME::Key)
 >
 > Return value: an array of lines of output
 > END
 >
 > I've attached a sample hook file if you want to have a play with it.
 > I'll document this all on the wiki if it gets accepted.
 >
 > I'll give you a few days to find some more problems, but if you fail
 > to find any then I'll package this up as a single patch and resubmit
 > it all.
 >
 > Hamish
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0001-Converted-crypto-to-use-the-gpgme-gem.patch
 Type: text/x-patch
 Size: 13172 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101128/256191b6/attachment-0004.bin>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0002-catch-exception-when-no-public-key-present.patch
 Type: text/x-patch
 Size: 1571 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101128/256191b6/attachment-0005.bin>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0003-improved-signature-messages.patch
 Type: text/x-patch
 Size: 2446 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101128/256191b6/attachment-0006.bin>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: 0004-added-signature-output-hook.patch
 Type: text/x-patch
 Size: 1395 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101128/256191b6/attachment-0007.bin>
 
 From sup-bugs@masanjin.net  Mon Nov 29 04:23:15 2010
 From: sup-bugs@masanjin.net (anonymous)
 Date: Mon, 29 Nov 2010 09:23:15 +0000
 Subject: [sup-devel] [issue134] Exception when scrolling down...
 In-Reply-To: <1291022595.09.0.312153163509.issue134@masanjin.net>
 Message-ID: <1291022595.09.0.312153163509.issue134@masanjin.net>
 
 
 New submission from anonymous:
 
 I scrolled down to a second page in my inbox while Sup was filling the top of
 the inbox having just polled for messages, and at about that time I got:
 
 --- RuntimeError from thread: load threads for thread-index-mode
 unknown drawable object: nil in #<Redwood::InboxMode:0x7fdcb829c538> for line 64
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/scroll-mode.rb:200:in `draw_line'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/line-cursor-mode.rb:52:in
 `draw_line'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/scroll-mode.rb:48:in `draw'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/scroll-mode.rb:48:in `each'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/scroll-mode.rb:48:in `draw'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/line-cursor-mode.rb:37:in `draw'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/buffer.rb:119:in `draw'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/buffer.rb:103:in `redraw'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/buffer.rb:341:in `draw_screen'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/util.rb:570:in `send'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/util.rb:570:in `method_missing'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:644:in
 `__unprotected_load_n_threads'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/thread.rb:334:in `load_n_threads'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:148:in `each_id_by_date'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each_id'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each_id'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:148:in `each_id_by_date'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/thread.rb:328:in `load_n_threads'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:640:in
 `__unprotected_load_n_threads'
 (eval):12:in `load_n_threads'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:624:in
 `load_n_threads_background'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:76:in `reporting_thread'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `initialize'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `new'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `reporting_thread'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:623:in
 `load_n_threads_background'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:694:in
 `__unprotected_load_threads'
 (eval):12:in `load_threads'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:89:in
 `initialize'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/line-cursor-mode.rb:22:in `call'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/line-cursor-mode.rb:22:in
 `initialize'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/line-cursor-mode.rb:22:in `each'
 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/
 
 ----------
 messages: 313
 nosy: anonymous
 priority: bug
 ruby_version: 1.8.7
 status: unread
 sup_version: 0.11
 title: Exception when scrolling down...
 
 _________________________________________
 Sup issue tracker <sup-bugs at masanjin.net>
 <http://masanjin.net/sup-bugs/issue134>
 _________________________________________
 
 From gaudenz@soziologie.ch  Mon Nov 29 04:41:35 2010
 From: gaudenz@soziologie.ch (Gaudenz Steinlin)
 Date: Mon, 29 Nov 2010 10:41:35 +0100
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 	<AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 	<1289932061-sup-96@meteor.durcheinandertal.local>
 	<AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
 	<AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
 Message-ID: <1291023322-sup-8457@meteor.durcheinandertal.local>
 
 Hi Hamish
 
 Excerpts from Hamish D's message of Son Nov 28 23:51:43 +0100 2010:
 > OK, here is a set of 4 patches that implement the change over to the
 > gpgme library. There's quite a bit of work in there so I thought I'd
 > leave it as a few patches, but I have done some tidying.
 
 I just discovered another problem: If the secret key is not available
 (because it's on a removable media and the media is not mounted), the
 mail is sent anyway. While this is just a bit annoying for signed mail
 it definitely should not happen for encrypted mails. Current sup
 corectly fails in this case.
 
 It would also be nice to have different colors for different trust
 levels. So you don't have to expand the extra information to see if a
 valid signature is trusted or not. Is this already possible with the
 current hook?
 
 > 
 > I have some more ideas for improvements, but I'm happy that this
 > reproduces the behaviour of using the gpg binary, and I find sup usage
 > much smoother with this change.
 > 
 > I'll leave it for others to decide whether to stick this in sup 0.12 -
 > I guess it could be risky to stick it in without it being tested, but
 > maybe it could be applied to the next tree, and then moved to main
 > after 0.12 has been released.
 
 As far as I understood the branch layout the flow of changes is master
 -> next -> release. So applying to next would mean it ends up in the
 next release (0.12).
 
 Gaudenz
 -- 
 Ever tried. Ever failed. No matter.
 Try again. Fail again. Fail better.
 ~ Samuel Beckett ~
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 482 bytes
 Desc: not available
 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101129/ee78612e/attachment.bin>
 
 From tero@tilus.net  Tue Nov 30 01:22:48 2010
 From: tero@tilus.net (Tero Tilus)
 Date: Tue, 30 Nov 2010 08:22:48 +0200
 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
 In-Reply-To: <1291023322-sup-8457@meteor.durcheinandertal.local>
 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
 	<AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
 	<AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
 	<1289466286-sup-7540@meteor.durcheinandertal.local>
 	<AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
 	<1289907535-sup-3989@meteor.durcheinandertal.local>
 	<AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
 	<1289932061-sup-96@meteor.durcheinandertal.local>
 	<AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
 	<AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
 	<1291023322-sup-8457@meteor.durcheinandertal.local>
 Message-ID: <1291097850-sup-6043@tilus.net>
 
 Gaudenz Steinlin, 2010-11-29 11:41:
 > As far as I understood the branch layout the flow of changes is
 > master -> next -> release. So applying to next would mean it ends up
 > in the next release (0.12).
 
 Master is considered "stable" and next "unstable".  Releases are
 tagged from master and small changes may go directly to master.  New
 features are introduced in next and merged to master when they are
 considered stable (enough).
 
 Applying to next would mean it ends up in 0.13 (or later if there are
 bugfix releases).
 
 --
 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
 
 From nicolas.pouillard@gmail.com  Tue Nov 30 08:01:35 2010
 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
 Date: Tue, 30 Nov 2010 05:01:35 -0800 (PST)
 Subject: [sup-devel] [issue133] add support for the mh mailbox format
 In-Reply-To: <1290856550.06.0.787394879314.issue133@masanjin.net>
 References: <1290856550.06.0.787394879314.issue133@masanjin.net>
 Message-ID: <4cf4f5af.8b02e30a.7219.ffff9349@mx.google.com>
 
 On Sat, 27 Nov 2010 11:15:50 +0000, anonymous <sup-bugs at masanjin.net> wrote:
 > 
 > New submission from anonymous:
 > 
 > I've been using the mh format (via nmh) for years, and it would be fantastic if 
 > sup could support it so people don't have to convert mailboxes to maildir or mbox 
 > to be able to use sup.
 
 I'm in favor of this feature as well. The nmh format for mailboxes is pretty
 simple, just directories of email files plus some (one?) special file that
 sup can just ignore. In other terms this is just maildir without their
 complicated naming conventions of files and directories.
 
 -- 
 Nicolas Pouillard
 http://nicolaspouillard.fr