Add a /no-progress switch to disable progress monitoring in Echo.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run a test with gallio.echo using /v:Quiet or /verbosity:Quiet

What is the expected output? What do you see instead?
I expect to see nothing at all.  Instead I see a slew of progress messages,
and it looks the exact same as if I specified "Normal"

What version of the product are you using? On what operating system?
Gallio Echo - Version 3.0.6 build 763, Windows XP SP2

Original issue reported on code.google.com by hecktarz...@gmail.com on 4 May 2009 at 2:30

[GoogleCodeExporter]

The verbosity argument refers to the messages logged by the Gallio runtime, 
rather
than the output of the console app, although I can appreciate the confusion. If 
you
run it with /v:Debug you should see the difference. There isn't currently any 
way to
suppress the progress messages, is that something you would be interested in?

Original comment by grahamr...@gmail.com on 4 May 2009 at 4:02

• Added labels: Component-Echo, Priority-Medium

[GoogleCodeExporter]

Ahh I see now.  May want to add something about the "log" in the verbiage.  I'm
running echo through a shared c# routine that collects the output so I was just
trying to save some memory :)  

Original comment by hecktarz...@gmail.com on 4 May 2009 at 4:53

[GoogleCodeExporter]

/verbosity:<level> Controls the level of detail of the information to display.  
The
available options are: 'Quiet', 'Normal', 'Verbose', 'Debug'.  (Short form: /v)

Yeah, currently this is very misleading as it says "Display" not "Log"

Original comment by hecktarz...@gmail.com on 4 May 2009 at 5:03

[GoogleCodeExporter]

The main difference I remember is that we have a log level called 
Important. Progress messages are logged with Important which 
iirc is now displayed in Quiet mode. That said you will still see the 
progress bar (when using Echo interactively) but it won't leave a 
trace in the summary.

There isn't much difference between logging and displaying as far 
as echois concerned. Filtering happens just before display using 
the verbosity to decide whether a message of given severity 
should be shown. This is a pretty typical design for command line 
tools. 

Original comment by jeff.br...@gmail.com on 4 May 2009 at 7:00

[GoogleCodeExporter]

Doh, nevermind about the progress monitor.  I forgot that the top line of the
progress message (the task name) just gets left behind by the progress 
monitoring
apparatus itself rather than being printed by the log.  Can't believe I wrote 
that
code only a year ago.  *sigh*

Thanks Graham for clearing that up.

In any case, I guess a good question is whether the rich console progress 
monitor
should somehow respond to verbosity or whether we should add a /no-progress 
option.

Original comment by jeff.br...@gmail.com on 5 May 2009 at 6:48

[GoogleCodeExporter]

Original comment by jeff.br...@gmail.com on 13 May 2009 at 11:50

• Changed title: Add a /no-progress switch to disable progress monitoring in Echo.
• Changed state: Accepted
• Added labels: Milestone-3.0.7, Type-Enhancement, Usability

[GoogleCodeExporter]

Fixed in v3.0.7

Original comment by jeff.br...@gmail.com on 14 May 2009 at 12:20

• Changed state: Fixed