Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: mailinglist@flasht.de (Christopher Bertels)
Subject: [sup-talk] Fixing header for encrypted messages (might be an old issue)
Date: Wed, 16 Sep 2009 00:42:04 +0200	[thread overview]
Message-ID: <1253054438-sup-8449@thinkpad-ubuntu> (raw)
In-Reply-To: <20090915222119.GA5290@chistera.yi.org>

Excerpts from Adeodato Sim?'s message of Mi Sep 16 00:21:19 +0200 2009:
> It's been like that all the time, but AFAIK only Mutt has problem
> opening those messages. FWIW, it's a bug in RMail (another one to add to
> the pile...):

Alright, good to know.

> I advice against using your patch, since it depends on broken behavior
> of RMail to produce correct results, and people may be using fixed
> versions of the library. For example, I uploaded fixed packages of RMail
> to Debian, and they'll become available in Ubuntu at some point.
> 
> Instead, you can find a patch to fix the issue in your system's RMail in
> one bugs linked above.

Alright, thanks. I'll just leave it for me like this until I've got a
new version of RMail then.

> > If this is an old issue and I'm just using an old version, feel free
> > to ignore this. I've tried using the current master or next branch,
> > but that causes a crash when trying to open encrypted emails. Maybe
> > someone else is having a similar problem?
> 
> No, I've recently started experiencing this as well, asuming you're
> talking about:
> 
> --- NoMethodError from thread: load messages for thread-view-mode
> undefined method `expandable?' for #<Array:0x7faa50e2d978>
> /home/dato/devel/sup/work/lib/sup/modes/thread-view-mode.rb:615:in `regen_text'
> /home/dato/devel/sup/work/lib/sup/modes/thread-view-mode.rb:610:in `each'
> /home/dato/devel/sup/work/lib/sup/modes/thread-view-mode.rb:610:in `regen_text'
> /home/dato/devel/sup/work/lib/sup/thread.rb:68:in `each'
> /home/dato/devel/sup/work/lib/sup/thread.rb:170:in `each_with_stuff'
> [...]

Yes, it's the same error I get. Any insights as to what is causing this?

Cheers,
Christopher.
-- 
================================
Christopher Bertels
http://www.adztec-independent.de
GPG Key ID: 0x2345b203
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090916/7f6fbfa9/attachment.bin>


  reply	other threads:[~2009-09-15 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 20:21 Christopher Bertels
2009-09-15 22:21 ` Adeodato Simó
2009-09-15 22:42   ` Christopher Bertels [this message]
2009-09-26 14:40     ` William Morgan
2009-09-26 14:49       ` William Morgan
2009-09-27 12:48         ` Adeodato Simó

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=1253054438-sup-8449@thinkpad-ubuntu \
    --to=mailinglist@flasht.de \
    /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