Done commands report nb_processed + nb_failed

[Christian Albaret]

Several command, such as copy or del, report
- each file as it is processed
- a possible error (to stderr)
- the number of files processed.

If the number of files is large, it can be difficult to spot errors in the flow of text.

Suggestion: in addition to the number of files processed, report also the number of files that failed (could also go to stderr).

 

[Charles Dye]

If the number of files is large, it can be difficult to spot errors in the flow of text.

Setting ErrorColors to something bright helps with this....

Suggestion: in addition to the number of files processed, report also the number of files that failed (could also go to stderr).

A worthwhile suggestion. Perhaps it could be hung on the /N switch, e.g. /NF for "Number of Failures"?

 

[Christian Albaret]

Setting ErrorColors to something bright helps with this....



A worthwhile suggestion. Perhaps it could be hung on the /N switch, e.g. /NF for "Number of Failures"?

I use an error color (red for instance), but you can still miss the error display if the number of files is really large (thousands) and the operation lasts for long (a minute, or more).

 

[Steve Fabian]

Christian Albaret wrote:
| ---Quote (Originally by Charles Dye)---
| Setting ErrorColors to something bright helps with this....
|
|
|
| A worthwhile suggestion. Perhaps it could be hung on the /N switch,
| e.g. /NF for "Number of Failures"? ---End Quote---
| I use an error color (red for instance), but you can still miss the
| error display if the number of files is really large (thousands) and
| the operation lasts for long (a minute, or more).

Try redirecting the error messages to a file, and in a separate TCC instance
you can use TAIL /F to watch them. Another possibility is to suppress the
success messages (or redirect them into a log file). For a whole-disk backup
I use the command (after a lot of suitable cleanup):

*copy/[!DESCRIPT.ION]/a:-d/fhjkuvxz/nejt/s/md c:\ d:\ >>&> %l.ERR | tee /a
%l.LOG

and watch error messages as suggested above.
--
HTH, Steve

 

[Christian Albaret]

Christian Albaret wrote:
| ---Quote (Originally by Charles Dye)---
| Setting ErrorColors to something bright helps with this....
|
|
|
| A worthwhile suggestion. Perhaps it could be hung on the /N switch,
| e.g. /NF for "Number of Failures"? ---End Quote---
| I use an error color (red for instance), but you can still miss the
| error display if the number of files is really large (thousands) and
| the operation lasts for long (a minute, or more).

Try redirecting the error messages to a file, and in a separate TCC instance
you can use TAIL /F to watch them. Another possibility is to suppress the
success messages (or redirect them into a log file). For a whole-disk backup
I use the command (after a lot of suitable cleanup):

*copy/[!DESCRIPT.ION]/a:-d/fhjkuvxz/nejt/s/md c:\ d:\ >>&> %l.ERR | tee /a
%l.LOG

and watch error messages as suggested above.
--
HTH, Steve

This is more suitable for batch files (or aliases), where you implement some handling in case of error. I was thinking about a simple information for the case of an interactive copy or move operation.