From: Tero Tilus <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue65] tput: No value for $TERM and no -T specified
Date: Tue, 09 Feb 2010 07:49:09 +0000 [thread overview]
Message-ID: <1265701749.73.0.531351997652.issue65@masanjin.net> (raw)
In-Reply-To: <1265701749.73.0.531351997652.issue65@masanjin.net>
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
parent reply other threads:[~2010-02-09 7:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1265701749.73.0.531351997652.issue65@masanjin.net>]
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=1265701749.73.0.531351997652.issue65@masanjin.net \
--to=sup-bugs@masanjin.net \
--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