From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs108864fga; Thu, 4 Mar 2010 08:37:25 -0800 (PST) Received: by 10.224.107.8 with SMTP id z8mr1226602qao.275.1267720638048; Thu, 04 Mar 2010 08:37:18 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si285868qwf.7.2010.03.04.08.37.17; Thu, 04 Mar 2010 08:37:17 -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 58AB01858321; Thu, 4 Mar 2010 11:37:17 -0500 (EST) Received: from tihlde.org (colargol.tihlde.org [158.38.48.10]) by rubyforge.org (Postfix) with ESMTP id B089C18582D3 for ; Thu, 4 Mar 2010 11:32:01 -0500 (EST) Received: by tihlde.org (Postfix, from userid 1623) id E9B1F1016A31; Thu, 4 Mar 2010 12:45:04 +0100 (CET) From: Helge Titlestad To: sup-talk In-reply-to: <1267654880-sup-4875@zyrg.net> References: <1267478622-sup-2939@tangerine.lanl.gov> <1267654880-sup-4875@zyrg.net> Date: Thu, 04 Mar 2010 12:45:04 +0100 Message-Id: <1267702902-sup-4834@tihlde.org> User-Agent: Sup/0.10.2 Subject: Re: [sup-talk] sup install error 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 Excerpts from Rich Lane's message of Wed Mar 03 23:23:06 +0100 2010: > I'm thinking about changing the gem dependency from ncursesw back to > plain ncurses to avoid these install failures. Anyone have thoughts on > this? If this breaks UTF-8 support more, I humbly vote against. UTF-8 with ncursesw might not be the perfect solution, but it seems to be the only solution at the moment, and anyone outside stricy ascii-writing countries will expect it to Just Work[tm]. -- alge _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk