From 0ea58e09465fff0badda27c31e00e27abadaaa17 Mon Sep 17 00:00:00 2001 From: Sam Moors Date: Fri, 19 Apr 2024 09:54:57 +0200 Subject: [PATCH] Update progress-bars.md --- docs/progress-bars.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/progress-bars.md b/docs/progress-bars.md index 07dfb813d..68204bb5b 100644 --- a/docs/progress-bars.md +++ b/docs/progress-bars.md @@ -11,7 +11,7 @@ The progress bars shown by EasyBuild are *dynamic*: they are only visible when t Note that for most progress bars each step is treated as being equal even though the time taken for the various steps varies. There are many factors that impact how long an individual installation step, installing -an easyconfig, or installing an extension may and this makes it very difficult to get a good estimate on how +an easyconfig, or installing an extension may take and this makes it very difficult to get a good estimate on how much time will be needed. The download progress bar is an exception here (as long as the size of the file to download could be determined first). @@ -102,7 +102,7 @@ This also makes `Rich` a *required* dependency for EasyBuild. Using '`basic`' as value for `output-style` results in basic output (no progress bars). By default `output-style` is set to '`auto`', which implies using the `Rich` Python package to produce -rich output (incl. progress bars) if is available, +rich output (incl. progress bars) if `Rich` is available, and falling back to using the basic output style if `Rich` is not available. ### `show-progress-bar`