What happened to the "Extract archive here, autodetect subfolder" option?

In Plasma 5 version of Dolphin there was an option to extract archive to catalogue named after the archive, but now it’s gone? Can I somehow re-add it to the context menu?
Plasma 5:

Plasma 6:
plasma6_dolphin_extract_options

The “Extract here” does that now.

3 Likes

To me “Extract here” does not do same as “… Autodetect subfolder” did . If I have an

  • archived folder, say “temp”
  • archive is named mypkg.tar.gz

The archive contents does not extract as mypkg/temp/ , but extracts to ./temp/ , to the current folder. That is also how the “Extract here” would imply it to do.

So, the original autodetect subfolder extraction is missing.

Also, this r/kde Reddit post would say the same.

(In light of this, I suggest dropping the “solution” checkmark.)

So, the original autodetect subfolder extraction is missing.

You are inverting things.

The original “Extract here” is missing now and replaced by the functionality formally known with name “Extract here autodetect subfolder”.

You can use “Extract To” to get what you’d like or in dolphin 24.08 there will be a move files to new directory context menu option, or you can add a service menu that does the old behavior.

Hmm, I not sure how I am inverting things? If the current subfolder extraction is not working as it used to, then the functionality as it used to be, is missing.

Now here you say that the original functionality can be optionally enabled in a future Dolphin release. So it would support what I was saying, that extraction to subfolder is not as it used to be.

1 Like

I don’t have a way to test this now, but I’m pretty sure that’s how “autodetect subfolder” worked in Plasma 5. So if you had an archive with one folder, then this folder would be unarchived in the current location. If there were more folders or files in the archive then a new folder would be created named after the archive and the archive contents would be unpacked there.
So if you have the mypkg.tar.gz archive with two folders - “foo” and “bar”, then the autodetect subfolder would create “mypkg” folder and put both “foo” and “bar” into it.
I was using the autodetect option by default, so this change doesn’t affect me much. But I can agree that the current naming convention is a bit confusing, especially when “extract here” usually means “do a mess, unarchive everything in this very location”. (So in the example above - put both “foo” and “bar” into current location.) Though I’m not sure if this topic is a place to complain about it.

Testing with Plasma 5.27.11 and Dolphin 23.08.5, the behavior of “autodetect subfolder” seems to be similar to the current “Extract here”; if there is a single subfolder in the archive, that subfolder is extracted as-is. The archive name is not used for folder name.

If there were more folders or files in the archive then a new folder would be created named after the archive

Indeed, this is how it worked in 5.27, so to be named after the archive, you need to have multiple subfolders. This is a bit confusing logic, as the behavior is different, depending on the contents of the package.

7-zip in Windows has this alternative action, to extract into archive-named subfolder, which is rather handy for duplicated archive contents, but archive packages having different names. If this will be what the Dolphin upgrade brings, I’ll be extra happy camper.

I agree, this is not inverting things, actually the new change is not an improvement:

  1. It is an inversion to how something worked for a long time.
  2. The UI is I guess nice for extract to but I don’t really want to think much about extracting files, so its nice for something I don’t think many people will use…
  3. The old language was fairly clear, now I have to do a search on the web to understand what is intended?

This is not better. It sounds like this can be added back manually as a custom option, however again, this is less convenient to a behavior that already worked very well…

Do you happen to know how to implement this particular command?

I looked at the commit and saw this was changed in the native code (cpp), the service menu solution requires dbus (point of failure, there are frequent issues with dbus e.g. crashing).

I also can’t configure this option either, I don’t want the option to delete my archive, this is actually an anti-feature to me. The archive is just that, an archive, not something annoying to be removed. And having that option in the menu is a great way to accidentally delete an archive…

I’m currently weighing how annoyed I am by this, maybe I should submit a different ticket to restore the previous behavior and configure this instead…

I was confused at first, too, but only because I was used to the “autodetect subfolder” option.

Now that I understand that the simple “Extract here” already takes care of not flooding the current folder with files, I think it is an improvement as we did away with needless option clutter.

When you actually want the current folder to be flooded with files without an intermediary folder to be created for you, then you can select “Extract to…” and then just confirm. I’d expect this to be a much more niche use-case, so putting it behind “Extract to…” rather than making it the default makes sense to me.

2 Likes