diff options
author | Karen Arutyunov <karen@codesynthesis.com> | 2019-01-24 21:41:48 +0300 |
---|---|---|
committer | Karen Arutyunov <karen@codesynthesis.com> | 2019-01-25 15:16:58 +0300 |
commit | 18bb25efa41dab4a3f7619040e2067da3533decd (patch) | |
tree | 822bd06dd0a9d5568c14862592d310fec1012b58 /bdep/common.cli | |
parent | a4dabaa6db8806f23bb7d7bdbb95cab456ef3a73 (diff) |
Add support for --no-progress option
Diffstat (limited to 'bdep/common.cli')
-rw-r--r-- | bdep/common.cli | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/bdep/common.cli b/bdep/common.cli index 4736159..2db2677 100644 --- a/bdep/common.cli +++ b/bdep/common.cli @@ -90,6 +90,23 @@ namespace bdep system." } + // 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. + // + bool --no-progress + { + "Suppress progress indicators for long-lasting operations, such as + network transfers, building, etc." + } + path --bpkg { "<path>", |