Hello g00r00!

Came to think of it -- is there any reason why Mystic on Windows (according to whatsnew.txt) doesn't sink stdout of archiver commands to NUL (> NUL), but rather just stderr (2> NUL)? That is, why it performs "2> NUL" instead of "> NUL 2>&1"?

Since -- isn't it so that any output from these commands will be shown to the user (possibly confusing the user and garbling the "screen" with a lot of technical mumbo-jumbo)? So one wants to avoid any such output to the user?

Granted that sinking stdout to /dev/null or NUL in general *does* create a problem for the archive View Cmd -- as the redirection to an output file will break... But this is easy to "fix" with a simple work-around for the View Cmd (e.g. for 7Z and ARJ):

Linux: command "%1" >> "%3%2" 2> /dev/null; exit $?
Windows: command "%1" >> "%3%2" 2> NUL || exit 1

The last one is a little "sloppy" as it doesn't capture the exact exit code on error. I believe it might be possible to capture the actual exit code also on Windows, but one would have to use delayed expansion, but I'm no expert in that area.

Just curious (as this is a difference for "external" archive viewing between Mystic on Linux and Windows).

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)