From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs26320fgb; Wed, 10 Mar 2010 10:00:34 -0800 (PST) Received: by 10.224.41.137 with SMTP id o9mr1340916qae.136.1268244034216; Wed, 10 Mar 2010 10:00:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si11923600qwf.7.2010.03.10.10.00.33; Wed, 10 Mar 2010 10:00:34 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 94B0818582F4; Wed, 10 Mar 2010 13:00:33 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 2EAA618581EF for ; Wed, 10 Mar 2010 12:59:49 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1NpQCC-00060Q-I6; Wed, 10 Mar 2010 12:59:48 -0500 From: Rich Lane To: Edward Z. Yang In-reply-to: <1268242549-sup-1852@ezyang> References: <1268196562-sup-1692@ezyang> <1268241639-sup-9685@zyrg.net> <1268242549-sup-1852@ezyang> Date: Wed, 10 Mar 2010 12:59:48 -0500 Message-Id: <1268243539-sup-5753@zyrg.net> User-Agent: Sup/git Cc: sup-devel Subject: Re: [sup-devel] Mysterious nil errors X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel