Covertly using the windows temp folder is not a really good idea.

[mzso]

Hi!

I'm usually short on space and I don't like files being moved needlessly between drives.

I would much prefer if anything was kept within the output folder while extracting then positioned properly when the process is finished.

[vatterspun]

I think this might make more sense as a feature request: optional ability to treat output folder as temp directory.

I wouldn't recommend making this a global change because local temp folders will often be substantially faster than an external device that might contain the file you're trying to extract. Doing everything entirely on that device could represent an intense performance hit: I recently tested a thumb drive that I expected to perform really well, but found it was roughly 12x slower than my local SSD.

[mzso]

@vatterspun commented on 2019. ápr. 12. 16:37 CEST:

I think this might make more sense as a feature request: optional ability to treat output folder as temp directory.

Makes no difference becuse it's still needed to be written back there if the output folder is there, you only use time because you need to copy it back where the stuff was extracted somewhere else. If the output folder is anywhere besides the system driver you only use time and copy twice needlessly.

[vatterspun]

copy twice needlessly

Sorry, yeah now I see what you're saying now. You might check out 7zip's explanation: https://7-zip.org/faq.html : "Why does drag-and-drop archive extraction from 7-Zip to Explorer use temp files?"?

There's also some useful discussion over on the SF.NET page: https://sourceforge.net/p/sevenzip/discussion/45797/thread/ed4d92ad/