Bug 483706

This is an intentional change. The "Extract here" option now does what "Extract here, autodetect subfolder" option used to do. Since, that's what most people expected to happen anyway, it's now the default.

> The "Extract here" option now does what "Extract here, autodetect subfolder" option used to do

Nope, not entirely. I assumed that was the case when I first saw that "extract here, autodetect subfolder" was removed, but there is a crucial difference.

Say I save the a file called mything.zip , whose contents are:
```
#contents of the zip file:

- mything
- - file1.txt
- - file2.txt
```
and I save it in a folder F where I also have a subfolder called "mything":
```
# my filesystem:

- /path/to/F
-- mything         #preexisting folder
-- mything.zip
```
Now say I want to unzip this file into a new subfolder, WITHOUT interfering with my existing folder.

When "autodetect subfolder" existed, which is the option I ALWAYS used, I could do either of two things:

1) I could do "extract here, autodetect subfolder", and this would create a folder "mything (1)", in order to avoid overwriting the existing folder of the same name, and it would extract the files into it, WITHOUT creating an additional folder inside of it, i.e. an additional level of nesting. Or
2) if I remember correctly (I'm almost sure) I could also rename the zip to somethingelse.zip, and do "extract here, autodetect subfolder", and this would extract the contents of the zip into a new folder called "somethingelse" WITHOUT an additional folder inside of it called "mything" (the name of the "root" or "pseudo-root" folder in the zip file).

NOW, with the current version, if I do "extract here", it extracts the files into the existing folder, prompting me for each file whether or not to overwrite the existing files (with the "apply to all" option of course).

This would be acceptable (or now that I think about it, it could be the solution) if it also prompted me at the beginning for whether or not I want to merge the extracted folder into the existing folder (just like when you attempt to copy a folder where there's already a folder of the same name) giving me the opportunity to choose a new name for it. But it does not. And if there weren't files with conflicting name, the whole thing would happen silently.

I think I was the one who reopened this as per comment 2, so I'm re-closing as I have filed a separate report:
https://bugs.kde.org/show_bug.cgi?id=504869