CLI: Generate verbose reports of actions

[MarcosSueiro]

E.g. a report of results of trying to embed MD5, including errors

[dericed]

I like this idea. Would you see this as a single document that stores the last x lines of operations? Or a log per session? In your case if you had such a log, what would you do with it? Just inspect it to audit past steps or store it?

[retokromer]

+1

In a little different context, we made good experiences with logs per session, which are processed during the final validation.

[MarcosSueiro]

I think log per session. What prompted the request was that after trying to embed MD5 on a large set of files it was nice to see which ones may have issues. It would be good to have such a log to share. But also for any command.

I guess xml would be ideal, but perhaps text would suffice?

E.g.

• Original command as typed
• Timestamp start, end
• Fail, success ratios
• Results (reading problems, bad file structure....)
• Verbose results per file (w timestamps)