TID: Mystic BBS 1.12 A47   
   MSGID: 2:201/137 fd6a5e46   
   REPLY: 1:129/215 f8cf6c49   
   TZUTC: 0200   
   Hello g00r00!   
      
   Thank you for your reply!   
      
   On 09 Aug 2021, g00r00 said the following...   
    g0>  BW> Windows: > NUL 2>&1   
    g0>  BW> Linux: > /dev/null 2>&1   
    g0>    
    g0> Mystic's local console API in Windows already takes over STDIN and   
    g0> STDOUT.   
      
   OK, but what happens to "external" archive viewers (View Cmd) on Windows then?   
      
   Won't their output be eaten up by the console API, resulting in (seemingly) no   
   contents inside those archives?   
      
   That's what currently happens for Linux, and the reason for needing a   
   construct like >> "%3%2" 2> /dev/null; exit $? at the end of the View Cmd on   
   Linux. Easy, but unnecessary, should Mystic instead only "eat" stderr of the   
   View Cmd on Linux. :)   
      
   Now, please don't get me wrong -- I think the job you've put into the archiver   
   stuff lately is marvelous, including the fix for the redirections, and I   
   appreciate it all very much! Just thinking that View Cmds would be easier to   
   construct if stdout wasn't eaten up (for View Cmds, only).   
      
   As always, thank you,    
      
   Best regards   
   Bj”rn   
      
   --- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)   
    * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 154/10 201/0 137 203/0 124 221/0 1 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 428 452 550 700 981 1016 1017 230/0 240/1120   
   SEEN-BY: 240/5411 5824 5832 5853 6309 249/206 307 317 400 280/464   
   SEEN-BY: 280/5003 282/1038 292/854 8125 301/1 317/3 320/219 322/757   
   SEEN-BY: 342/200 396/45 633/280 2452/250 2454/119 3634/24   
   PATH: 201/137 0 203/0 280/464 240/5832 229/426