From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Mysterious nil errors
Date: Wed, 10 Mar 2010 13:06:19 -0500 [thread overview]
Message-ID: <1268244332-sup-8923@ezyang> (raw)
In-Reply-To: <1268243539-sup-5753@zyrg.net>
Excerpts from Rich Lane's message of Wed Mar 10 12:59:48 -0500 2010:
> If header['content-type'] == "" then it counts as true in ruby. Maybe
> you wanted to check empty? instead? This is an rmail bug, so I think
> instead of adding workarounds to our code we should monkeypatch rmail to
> fix it.
Heh, my ruby-fu isn't quite there yet; I just hacked around until I made all of
the errors go away. :-) Monkeypatching the rmail code would not be a bad
proposition.
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-03-10 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 4:50 Edward Z. Yang
2010-03-10 4:52 ` Edward Z. Yang
2010-03-10 6:43 ` Tero Tilus
2010-03-10 17:24 ` Rich Lane
2010-03-10 17:40 ` Edward Z. Yang
2010-03-10 17:59 ` Rich Lane
2010-03-10 18:06 ` Edward Z. Yang [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=1268244332-sup-8923@ezyang \
--to=ezyang@mit.edu \
--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