If TERM is not set you get a lot of spurious errors coming from tput #9
Description
What steps will reproduce the problem?
1. unset TERM
2. try using msg command
3. note tput errors
What is the expected output? What do you see instead?
The script should do something sane like not try to use tput if the TERM
environment variable is unset.
What version of the product are you using? On what operating system?
2.00-beta-3 on Linux and OS X
Please provide any additional information below.
See attached patch.
Original issue reported on code.google.com by benjamin...@gmail.com on 24 Jun 2013 at 11:31