From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs565808agb; Sat, 19 Dec 2009 11:08:28 -0800 (PST) Received: by 10.224.24.212 with SMTP id w20mr3056819qab.229.1261249707903; Sat, 19 Dec 2009 11:08:27 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 27si7069326qyk.123.2009.12.19.11.08.27; Sat, 19 Dec 2009 11:08:27 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id AE1E11D78875; Sat, 19 Dec 2009 14:08:27 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id BD55A1858304 for ; Sat, 19 Dec 2009 14:06:18 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NM4d8-000107-2g for sup-talk@rubyforge.org; Sat, 19 Dec 2009 11:06:18 -0800 From: William Morgan To: sup-talk In-reply-to: <80055d7c0912141351q4313a3fbp71b1974b1adeae42@mail.gmail.com> References: <20091214212804.GA4198@linux-vk5u.ben.pri> <80055d7c0912141351q4313a3fbp71b1974b1adeae42@mail.gmail.com> Date: Sat, 19 Dec 2009 11:06:18 -0800 Message-Id: <1261249415-sup-7810@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] Crash of Sup 0.9.1 X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Andrei Thorp's message of 2009-12-14: > As a somewhat obvious thing to say, I would guess that your ruby > ncurses or ncurses is too old/new. Try upgrading your ncurses stuff -- > might help. I think this is probably correct---there's something screwey about your ncurses gem. Are you running Ruby 1.9 by any chance? -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk