TID: Mystic BBS 1.12 A47   
   MSGID: 2:201/137 9a380c67   
   REPLY: 2:201/137 95462887   
   TZUTC: 0200   
   Hello again, g00r00!   
      
   On 06 Aug 2021, Bj”rn Wiberg said the following...   
    BW>  BW> For instance, tar requires the "correct" (full) path of a file within   
    BW>  BW> archive to be entered when selecting files for extraction.   
    BW>    
    BW> Apart from tar, this also applies to zip, lha and 7z (including LHA/LZH   
    BW> via 7-ZIP for Windows).   
    BW>    
    BW> (But not to arj e -e, zoo x:, or arc e which doesn't have any notion of   
    BW> subdirectories whatsoever).   
      
   OK, a clarification might be in place:   
      
   The problem is only with the sanitization of the file name that one can   
   specify manually when choosing to (D)ownload (prompt #304) for an archiver   
   which has no built-in archive browser in Mystic.   
      
   So this does *not* affect archives which have built-in viewing support (ZIP,   
   LHA/LZH and RAR), as the path passed in %2 to the Unpack Cmd in those cases   
   *is* fully qualified.   
      
   So, in practice, on a default installation, this only concerns 7z (and LHA via   
   7z on Windows).   
      
   And any "picky" custom archivers one might have added after that, such as tar.   
   :)   
      
   Best regards   
   Bj”rn   
   --- Mystic BBS v1.12 A47 2021/08/05 (Linux/64)   
    * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)   
   SEEN-BY: 1/123 30/0 80/1 90/1 103/705 105/81 120/340 123/131 124/5016   
   SEEN-BY: 129/305 154/10 201/0 137 203/0 124 218/700 221/0 1 6 226/30   
   SEEN-BY: 227/114 702 229/101 424 426 428 452 550 700 981 1016 1017   
   SEEN-BY: 230/0 240/1120 5832 249/206 307 317 400 261/38 280/464 5003   
   SEEN-BY: 282/464 1038 292/854 8125 301/0 1 101 113 317/3 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 633/280 712/848 920/1 2452/250   
   SEEN-BY: 3634/24 5020/1042 5058/104   
   PATH: 201/137 0 203/0 280/464 301/1 229/426