https://bugs.kde.org/show_bug.cgi?id=451032

Fabian Vogt <fab...@ritter-vogt.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|REPORTED                    |NEEDSINFO

--- Comment #2 from Fabian Vogt <fab...@ritter-vogt.de> ---
> /home/myname/.cache/kioexec/krun/5331_0/index.php

Yeah, that's the kioexec fallback path which shouldn't be used in most cases.
If you can get this reliably, please tell how.

> /run/user/1000/doc/4578b2a5/index.php

That's a location from the xdg-document-portal. Whether that is used is
entirely up to the application. It might be used if e.g. an URL is passed
somewhere.

(In reply to Rafael Linux User from comment #1)
> I would like to add to this, and to solve two related problems. 
> 
> My daily work is on remote FTP servers using Krusader and Visual Studio Code
> (VSC). At home session, kio-fuse (Krusader) creates a different reference
> kio-fuse-XXXXXXXX (where XXXXXXXX are letters) to the same FTP connection.
> While this is not a problem in principle, it is a problem when opening
> "Trusted Folders" in VSC. VSC allows folders to be assigned the "trusted"
> attribute, so that on subsequent accesses to that folder, it will trust its
> contents. 
> 
> By assigning kio-fuse different local references (kio-fuse-XXXXXXXX), VSC
> understands that it is a different folder and loses the trust it had with
> it. This would be avoided if the same reference (local path) was always
> assigned by kio-fuse to remote folders based, for example, on the HASH
> produced by "ftp://server/folder";. 
> 
> Please, take it into account.

That's https://bugs.kde.org/show_bug.cgi?id=432856 resp.
https://invent.kde.org/system/kio-fuse/-/issues/18.

The locations within kio-fuse's mount are deterministic and constant, only
the temporary mountpoint changes.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to