Hmm I don't know, this might break some workflows :/
Basically with "autodetect subfolder" you can always assume that a folder will be created and some poeple might rely on this.

What is your motivation for this change?

In D23693#528249, @elvisangelaccio wrote:

Hmm I don't know, this might break some workflows :/
Basically with "autodetect subfolder" you can always assume that a folder will be created and some poeple might rely on this.

What is your motivation for this change?

When you have a single file archive and you extract it using autodetect, it creates a folder with the file in it.
Then you need to open the dir to discover that there is a single file.
A common pattern of mine (and I guess others) has been to discover that there had only one file, and right after cut it to its parent folder and deleting the folder.
A workaround is to open the archive and in case there is one file using "Extract here" and if not "Extract autodetect".
But it is a long process that negates the use of "Extract autodetect" as a short path feature.

It seems to me the change of behavior justifies itself in that it will most likely improve users workflow for single file archives.

Do you have an opinion @ngraham ?

ping