Feature Request: Better Progress Output

[GoogleCodeExporter]

Watching a cursor blink for 20+ minutes and *hoping* the program you're running 
is doing something and didn't just hang is a little unsettling. It's nice to be 
able to monitor (or at least get some sense) of the progress of any program 
that might take a particularly long time to complete execution (as is the case 
with boar when importing large directories).

Having a --progress switch, varying levels of verbosity (ie. -v, -vv, ..), or 
even a --debug switch (along the lines of wget) to print some sort of progress 
output to the console would be much appreciated.

Even if there's a performance hit, for those that choose to enable it, having a 
(processed/total) style progress indicator can be very nice especially on huge 
imports as otherwise there is zero way to gage how far along boar is (or that 
it is infact making progress during certain phases like the initial hash 
calculation).

Thanks :) 

Original issue reported on code.google.com by cryptob...@gmail.com on 21 Dec 2011 at 5:15

[GoogleCodeExporter]

Agreed, this is a highly desirable feature.

Original comment by ekb...@gmail.com on 21 Dec 2011 at 8:42

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

There are now progress printed by default for the initial scan for changes 
(used for commands "update", "ci", "import" and "status"). During file 
operations, files are listed as they are processed ("ci", "co", "import").

Fixed as of changeset 57c3f8addc7e.

Original comment by ekb...@gmail.com on 12 Feb 2012 at 6:48

• Changed state: Verified

[GoogleCodeExporter]

Issue 49 has been merged into this issue.

Original comment by ekb...@gmail.com on 12 Feb 2012 at 9:06