Docs: Removed references to $TERM, which is irrelevant anyway

doc/man/task-color.5.in

@@ -4,22 +4,9 @@
 task-color \- A color tutorial for the Taskwarrior command line todo manager.
 
 .SH SETUP
-The first thing you need is a terminal program that supports color.  All
+The first thing you need is make sure you tell Taskwarrior that you want to use
-terminal programs support color, but only a few support lots of colors.  First
+color.  This is the default for Taskwarrior, so the following step may be
-tell your terminal program to use color by specifying the TERM environment
+unnecessary.
-variable like this:
-
-    TERM=xterm-color
-
-In this example, xterm-color is used - a common value, and one that doesn't
-require that you use xterm.  This works for most setups.  This setting belongs
-in your shell profile (~/.bash_profile, ~/.bashrc, ~/.cshrc etc, depending on
-which shell you use).  If this is a new setting, you will need to either run
-that profile script, or close and reopen the terminal window (which does the
-same thing).
-
-Now tell Taskwarrior that you want to use color.  This is the default for
-Taskwarrior, so the following step may be unnecessary.
 
     $ task config color on
 

src/commands/CmdDiagnostics.cpp

@@ -398,15 +398,12 @@ int CmdDiagnostics::execute (std::string& output)
   out << bold.colorize (STRING_CMD_DIAG_TESTS)
       << '\n';
 
-  // Determine terminal details.
+  // Report terminal dimensions.
-  const char* term = getenv ("TERM");
+  out << "   Terminal: "
-  out << "      $TERM: "
-      << (term ? term : STRING_CMD_DIAG_NONE)
-      << " ("
       << context.getWidth ()
       << 'x'
       << context.getHeight ()
-      << ")\n";
+      << '\n';
 
   // Scan tasks for duplicate UUIDs.
   auto all = context.tdb2.all_tasks ();