Hello g00r00!

It is my understanding that the Unpack Cmd of archivers should junk paths to make sure that Mystic will find the extracted file in the root of the temp directory, e.g. when (V)iewing an archive (non-built-in formats) and choosing to (D)ownload a file. Is that correct?

As you already know, some archivers (e.g. tar) require archive members to be specified by their full path when extracting parts of (specific files from) an archive.

Right now I'm having the issue that albeit I can specify the path to an archive member at the (D)ownload file name prompt -- e.g. subdir/test2.txt -- which is great! -- the extracted file will (because of "junk path" flags to the
archiver) end up as test2.txt in the top of the temp directory. Mystic fails to find the file as subdir/test2.txt inside the temp directory, and does nothing (you get no file).

If you (D)ownload again, and this time specify test2.txt, it will actually fail to extract it (you didn't specify a full path this time!), but find the previously junk-path-extracted test2.txt, and give you that for download.

Shouldn't Mystic be looking for the basename of the entered File Name when trying to locate the extracted file for download?

(But *do* allow for the entered File Name to be a path -- just as it is now! -- as some archivers require it.)

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Shouldn't Mystic be looking for the basename of the entered File Name
when trying to locate the extracted file for download?

It absolutely should, good call! I have changed it to strip the path after it does the extract during the ASCII view Download in the next build!

... A black cat crossing your path signifies that the animal is going somewhere

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

Hello g00r00!

On 08 Aug 2021, g00r00 said the following...

Shouldn't Mystic be looking for the basename of the entered File Name when trying to locate the extracted file for download?

It absolutely should, good call! I have changed it to strip the path after it does the extract during the ASCII view Download in the next build!

Thanks a lot! It is much appreciated! :)

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

Hope all is well with you!

On 08 Aug 2021, g00r00 said the following...

Shouldn't Mystic be looking for the basename of the entered File Name when trying to locate the extracted file for download?

It absolutely should, good call! I have changed it to strip the path after it does the extract during the ASCII view Download in the next build!

You probably know this already :), but the latest prealpha (which is a couple of days old now) appears to disallow anything with a path (slash) in it at the archive (V)iewer (D)ownload File Name prompt, i.e. it does not even call the archiver (e.g. tar) if you enter a path as part of the filename.

So, kind of a regression there, as the one from Aug 08 allowed a path (but did not perform basename when locating the file to send to the user).

Just let me know if/when you want me to test something related to this (also the new prompt), and I'll be happy to help!

Best regards
Bj”rn
--- Mystic BBS v1.12 A47 2021/08/10 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

You probably know this already :), but the latest prealpha (which is a couple of days old now) appears to disallow anything with a path (slash) in it at the archive (V)iewer (D)ownload File Name prompt, i.e. it does not even call the archiver (e.g. tar) if you enter a path as part of the filename.

I redid all of that stuff in the next build I just haven't had time to work on anything since and I haven't released it yet.

... Consultant: A person who makes good on a salesman's promises!

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

Hello g00r00!

On 14 Aug 2021, g00r00 said the following...

I redid all of that stuff in the next build I just haven't had time to work on anything since and I haven't released it yet.

Thank you, g00r00 -- sounds great. You're the best! :)

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/10 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

On 15 Aug 2021, Bj”rn Wiberg said the following...

I redid all of that stuff in the next build I just haven't had time t work on anything since and I haven't released it yet.

Thank you, g00r00 -- sounds great. You're the best! :)

I can confirm that (D)ownload of a file from a subdirectory inside a tar file from the "external" archive (V)iewer indeed works as intended now with the latest build.

The %2 file name is passed correctly to the archiver (tar), and the
resulting extracted file (which I make sure tar junks the path for when extracting) is correctly found by its basename, and sent.

Thanks a lot for fixing this!

Only the "illegal filename" prompt left of all this archiver stuff, then -- then hopefully the archiver section of Mystic will live happily ever after. :)

Thanks again!

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/15 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

On 15 Aug 2021, g00r00 said the following...

Only the "illegal filename" prompt left of all this archiver stuff, t

I'll get that in for you today!

Thanks a lot! I'll try to install the latest one shortly.

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/15 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

On 18 Aug 2021, Bj”rn Wiberg said the following...

Only the "illegal filename" prompt left of all this archiver stu

I'll get that in for you today!

Thanks a lot! I'll try to install the latest one shortly.

Installed now, and everything seems to be working just fine! Thanks a lot!

Oh, I forgot to ask, will the length of archiver command lines possibly be extended in the future, or should I perhaps create a tar wrapper to stuff in all extra (and unfortunately long) flags for tar?

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/17 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Oh, I forgot to ask, will the length of archiver command lines possibly
be extended in the future, or should I perhaps create a tar wrapper to stuff in all extra (and unfortunately long) flags for tar?

I can extend them in the future but for now they're stuck at 80 characters so you might have to make a .sh file if you need them to be longer.

I've already done the data revisions for A47 so it will have to come in A48 if I extend the length.

... A book in the hand is worth two on the shelf!

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

Hello g00r00!

Thank you for your reply!

On 19 Aug 2021, g00r00 said the following...

I can extend them in the future but for now they're stuck at 80
characters so you might have to make a .sh file if you need them to be longer.
I've already done the data revisions for A47 so it will have to come in A48 if I extend the length.

No worries! Thanks!

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/17 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)