Subj : Re: Unpack Cmd %2 and paths (another follow-up)
To   : g00r00
From : Bj”rn Wiberg
Date : Fri Aug 06 2021 03:00 pm

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)

.