Add --progress common option

1 files changed, 16 insertions, 8 deletions

diff --git a/bdep/common.cli b/bdep/common.cli
index cff5790..cdf0e2c 100644
--- a/bdep/common.cli
+++ b/bdep/common.cli
@@ -91,15 +91,23 @@ namespace bdep
 
     // When it comes to external programs (such as curl, git, etc), if stderr
     // is not a terminal, the logic is actually tri-state: With --no-progress
-    // we suppress any progress. With --progress (which we may add in the
-    // future), we request full progress. Finally, without any --*progress
-    // options we let the external program decide what to do: it may do
-    // something intelligent (like curl) and produce non-terminal-friendly
-    // progress (such as status lines printed periodically) or it may disable
-    // progress all together (like git). Of course, it may also do no
-    // detection and dump non-terminal-unfriendly progress in which case we
-    // should probably do the detection ourselves and suppress it.
+    // we suppress any progress. With --progress, we request full progress.
+    // Finally, without any --*progress options we let the external program
+    // decide what to do: it may do something intelligent (like curl) and
+    // produce non-terminal-friendly progress (such as status lines printed
+    // periodically) or it may disable progress all together (like git). Of
+    // course, it may also do no detection and dump non-terminal-unfriendly
+    // progress in which case we should probably do the detection ourselves
+    // and suppress it.
     //
+    bool --progress
+    {
+      "Display progress indicators for long-lasting operations, such as
+       network transfers, building, etc. If printing to a terminal the
+       progress is displayed by default for low verbosity levels. Use
+       \cb{--no-progress} to suppress."
+    }
+
     bool --no-progress
     {
       "Suppress progress indicators for long-lasting operations, such as