From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.213.28.69 with SMTP id l5cs149688ebc;
        Mon, 8 Feb 2010 23:49:17 -0800 (PST)
Received: by 10.224.65.81 with SMTP id h17mr2945895qai.112.1265701756973;
        Mon, 08 Feb 2010 23:49:16 -0800 (PST)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 8si4367750qwj.51.2010.02.08.23.49.16;
        Mon, 08 Feb 2010 23:49:16 -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 7476418582DD;
	Tue,  9 Feb 2010 02:49:16 -0500 (EST)
Received: from entry.masanjin.net (masanjin.net [209.20.72.13])
	by rubyforge.org (Postfix) with ESMTP id 54CE618582CE
	for <sup-devel@rubyforge.org>; Tue,  9 Feb 2010 02:49:12 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=entry.masanjin.net)
	by entry.masanjin.net with esmtp (Exim 4.69)
	(envelope-from <roundup-admin@masanjin.net>) id 1NekqM-0004K2-4Q
	for sup-devel@rubyforge.org; Tue, 09 Feb 2010 02:49:12 -0500
MIME-Version: 1.0
To: sup-devel@rubyforge.org
From: Tero Tilus <sup-bugs@masanjin.net>
Date: Tue, 09 Feb 2010 07:49:09 +0000
Precedence: bulk
X-Roundup-Name: Sup issue tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.4.10
Message-Id: <1265701749.73.0.531351997652.issue65@masanjin.net>
X-Roundup-issue-status: unread
X-Roundup-issue-priority: bug
In-Reply-To: <1265701749.73.0.531351997652.issue65@masanjin.net>
Subject: [sup-devel] [issue65] tput: No value for $TERM and no -T specified
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Reply-To: Sup issue tracker <sup-bugs@masanjin.net>,
	Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-devel-bounces@rubyforge.org
Errors-To: sup-devel-bounces@rubyforge.org


New submission from Tero Tilus <tero@tilus.net>:

Sup-dump complains

  tput: No value for $TERM and no -T specified

when run from cron.  This is caused by terminal colors monkeypatch to Curses in
sup/colormap.rb.  Either sup.rb should not expect $TERM or sup-dump should not
`require "sup"`.  Which way to go?

----------
messages: 161
nosy: terotil
priority: bug
ruby_version: ruby 1.8.7 (2008-08-11 patchlevel 72)
status: unread
sup_version: git next
title: tput: No value for $TERM and no -T specified

_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue65>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel