arguments -t or -c not recognized

Question

arguments -t or -c not recognized

unalignedcoder opened this issue a year ago · comments

unalignedcoder commented a year ago

There seem to be a contradiction between instructions and reality

I really wanted to use that -t argument but it won't let me.

HelpSeeker · Answer 1 · Fri May 26 2023 22:22:20 GMT+0800 (China Standard Time)

Did you download the zip from the release page? Because that version is almost 5 years old by now.

unalignedcoder · Answer 2 · Fri May 26 2023 23:34:01 GMT+0800 (China Standard Time)

Okay where from then kind sir

onioneffect · Answer 3 · Sat May 27 2023 00:11:10 GMT+0800 (China Standard Time)

Code -> Download ZIP

unalignedcoder · Answer 4 · Sat May 27 2023 23:14:48 GMT+0800 (China Standard Time)

It works as intended now, but why does it create two folders from the same thread, one in /downloads and the other in /new?

onioneffect · Answer 5 · Sun May 28 2023 00:59:38 GMT+0800 (China Standard Time)

It works as intended now, but why does it create two folders from the same thread, one in /downloads and the other in /new?

This is exactly what the author intended: #34 (comment)

This is unrelated, but I have noticed a bug that causes files to be downloaded both to downloads/ and new/, creating duplicates. I think (?) it was introduced by one of my changes because it didn't happen before I ever contributed to the project. This is a subject for a whole new ticket.

Exceen · Answer 6 · Sun May 28 2023 04:49:36 GMT+0800 (China Standard Time)

why does it create two folders from the same thread, one in /downloads and the other in /new?

If you delete a file in the /downloads folder, the script handles this situation as if the file was never downloaded at all. That means that if the file doesn't exist in /new folder either, it will be downloaded into both folders again. If you only delete the file in the /new folder, nothing happens at all.

The reason for this behavior is that I wanted a full archive of a thread (which is inside the /downloads folder) and additionally to that I wanted to just keep the files I actually want to keep and remove the rest (which is the /new folder essentially).

The /downloads folder basically just memorizes which files have already been downloaded so that the script can determine which files in the thread are new and still need to be downloaded. In theory you could just save a list of already downloaded files into a json-file instead of storing the full file in the /downloads folder.

unalignedcoder · Answer 7 · Sun May 28 2023 10:28:01 GMT+0800 (China Standard Time)

I didn't delete any files, yet this thread had all its content duplicated from the start:

That's a 200mb folder twice. Is this intentional? If the /downloads folder is used only for reference, perhaps it could use the thumbnails, instead of the full file?

unalignedcoder · Answer 8 · Sun May 28 2023 10:56:43 GMT+0800 (China Standard Time)

As a quick workaround, I've added the -b --backup argument:

without the -b, it only saves images in /downloads

Exceen · Answer 9 · Sun May 28 2023 17:24:18 GMT+0800 (China Standard Time)

That's a 200mb folder twice. Is this intentional? If the /downloads folder is used only for reference, perhaps it could use the thumbnails, instead of the full file?

This is intended, yes.

As a quick workaround, I've added the -b --backup argument:

without the -b, it only saves images in /downloads

I might push something later to omit the /new folder.

Exceen · Answer 10 · Wed May 31 2023 05:43:29 GMT+0800 (China Standard Time)

added --no-new-dir argument