Hello g00r00!

Just a quick follow-up on this (in case someone else is also adjusting their archiver configurations, and to write it down) --

On 03 Aug 2021, Bj”rn Wiberg said the following...
 BW>    Pack Cmd ³ arj a -e -i -y "%1" "%2"
 BW>  Unpack Cmd ³ arj e -e -i -y -w"%3" "%1" "%2"
 BW>    View Cmd ³ arj l -i -y "%1" >> "%3%2" 2> /dev/null; exit $? >>

Those should be:

  Pack Cmd ³ arj a -e -i -y "%1" "%2" >>
Unpack Cmd ³ arj e -e -i -y -w"%3" "%1" "%2" >>
  View Cmd ³ arj l -i -y "%1" >> "%3%2" 2> /dev/null; exit $? >>

Note the added >> to chain with Mystic's addition of /dev/null etc.
Otherwise arj will interpret /dev/null as an additional filename.

 BW>      Pack Cmd ³ 7z a -y "%1" "%2"
 BW>    Unpack Cmd ³ 7z e -y -o"%3" "%1" "%2"
 BW>      View Cmd ³ 7z l -ba -y "%1" >> "%3%2" 2> /dev/null; exit $? >>

Those should be:

   Pack Cmd ³ 7z a -ba -y "%1" "%2" >>
 Unpack Cmd ³ 7z e -ba -y -o"%3" "%1" "%2" >>
   View Cmd ³ 7z l -ba -y "%1" >> "%3%2" 2> /dev/null; exit $? >>

Note the added -ba to get rid of CPU stats etc, and >> to chain with Mystic's addition of /dev/null etc. Otherwise 7z will interpret /dev/null as an additional filename.

All this makes me wonder if the other archivers would need the same thing (>>)? Or if perhaps this should have been added by Mystic instead?

I found the following in whatsnew.txt:

 + When executing archives, MUTIL in Unix will now automatically append
   " /dev/null 2>&1" to the end of each archive execution command in order
   to hide standard output and error messages.  It was already adding "2>nul"
   in Windows.

Perhaps this should have been ">> /dev/null 2>&1" instead?

Best regards
Bj”rn

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