1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

commands report nb_processed + nb_failed

Discussion in 'Suggestions' started by Christian Albaret, Feb 17, 2009.

  1. Christian Albaret

    Joined:
    Jul 1, 2008
    Messages:
    154
    Likes Received:
    1
    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).
     
  2. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,307
    Likes Received:
    39
    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"?
     
  3. Christian Albaret

    Joined:
    Jul 1, 2008
    Messages:
    154
    Likes Received:
    1
    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).
     
  4. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    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
     
  5. Christian Albaret

    Joined:
    Jul 1, 2008
    Messages:
    154
    Likes Received:
    1
    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.
     

Share This Page