Summary: | Dolphin "Open Folder With" uses wrong working directory | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Frank Märkle <FrankMaerkle> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | minor | CC: | kfm-devel, nicolas.fella |
Priority: | NOR | ||
Version: | 22.08.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Frank Märkle
2022-11-27 22:43:05 UTC
I can confirm the behavior. Relevant line is https://invent.kde.org/frameworks/kio/-/blob/master/src/gui/kprocessrunner.cpp#L139. It uses the URL minus the file name as working dir. That said I'm not sure how much of a bug this is. > This leads to various applications not opening the expected folder. What applications exactly? Any app that expects a file/folder URL to be passed really should define a placeholder for it Thanks for looking into this.
> That said I'm not sure how much of a bug this is.
> What applications exactly? Any app that expects a file/folder URL to be passed really should define a placeholder for it
I just tested it again, and realized that the correct path is passed as the first parameter, even without the %u placeholder. During my initial testing, I thought users would need to know that %u syntax to get the correct path, which I did not know for quite some time.
So, then it is only really relevant for quick-and-dirty scripts which work directly within the working directory.
And I guess, one could expect users to grab the directory in their scripts from $1, if they want to use them in .desktop-files for processing directories.
My personal intuition would still be to fix it, just to eradicate the possibility of unexpected behavior, but I understand that this is a breaking change for whoever might be relying on this unusual behavior.
|