https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #60 from Christian (Fuchs) <k...@fuchsnet.ch> --- (In reply to Nate Graham from comment #59) > (In reply to Christian (Fuchs) from comment #57) > > As per the blog post, it will make its way into 22.04, so we have to wait > > roughly 5 months for it to appear. > > From what I can see in > > ttps://invent.kde.org/utilities/ark/-/merge_requests/80 it only went into > > master, why a one-liner with an additional included header (that seems to be > > available unrelated to the change) is not backported is a bit beyond me, but > > there is at least the hope that some packagers might patch it in the > > meantime. > Backported; it should show up in 21.12.1. > > Still I'm not sure it's the permanent fix for this issue here. Wanting a > file manager window to open after extraction in Ark is different from > whether you want this in Dolphin, since when you invoke the functionality in > Dolphin, you still have a file manager window open. Hi Nate, thank you very much for backporting. As for long term: I assume you mean that if the user doesn't come from dolphin, but rather from ark directly, it should open a window? I'd agree that the option in ark should modify that behaviour, and maybe not the one in dolphin. However, I assume this is very much the minority of cases, I assume most users that do extract compressed files via GUI do come from a file manager, in our case dolphin, and not open ark directly. So as a default behaviour in the meantime, I think following that option is the least bad option. As for dolphin: given we control the desktop file which creates that service menu, it would be simple to have the command modified to open the default file manager. However, getting the target folder might be more difficult, since that is something ark knows about, but dolphin doesn't. So maybe the option is two-fold: 1) Add a command line switch to ark which does, after extraction, open the default (or specified) file browser in the target directory once done 2) Use that switch in whatever command the context menu invokes 3) Make that behaviour configurable, which is probably tricky, but technically could be done by having two different context menu entries, then users can choose with the options for context menus dolphin already provides. -- You are receiving this mail because: You are watching all bug changes.