Subj : Re: Redirecting only stderr to NUL on Windows? (suggested fix)
To   : Bj”rn Wiberg
From : g00r00
Date : Mon Aug 09 2021 04:16 pm

 BW> That's what currently happens for Linux, and the reason for needing a
 BW> construct like >> "%3%2" 2> /dev/null; exit $? at the end of the View
 BW> Cmd on Linux. Easy, but unnecessary, should Mystic instead only "eat"
 BW> stderr of the View Cmd on Linux. :)

The intention here is to block STDOUT because redirecting raw output of STDOUT from an archive utility was something I considered a security risk.  It will likely expose all of the directory structure of your system which makes it easier to exploit (if one were to exist).

The external view command is intended to populate the archive data into the temporary display file and then Mystic displays that file.  How that data gets into the file is not up to Mystic, its up to whatever program the view command executes. That is the desired implementation of external viewer support.

(There is also an unfinished scripted view extension that works with the ANSI viewer to allow external archivers to use the full ANSI viewer functionality. I need to get that done one of these days)

I could change it in Linux to only suppress STDERR just for view but then when someone does set up an archive viewer in the intended way, Mystic is going to show its output (by default) which would be undesired and potentially unsecure. 
Mystic is trying to err on th side of security but it still allows you to do both a direct redirection like you are doing too - it just defaults to being conservative in this situation and makes you work a little more to do a STDOUT redirect.

.... WOMAN.ZIP - Great program but no documentation

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.