https://bugs.kde.org/show_bug.cgi?id=432856
silopolis <silopo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |silopo...@gmail.com
--- Comment #11 from silopolis <silopo...@gmail.com> ---
Hi, may I heavily pound on this one?!
My take on this is that a[nother] "$HOME/$KIO_FUSE_ROOT" mount directory is
needed for stable/permanent mounts.
Actually, I'm using smb4k just because kio-fuse doesn't allow me to configure a
stable mount path to some SMB shares I _need_ to find always in the same place,
not to mention the other issues already evoked in this thread.
But what about the other protocols?
It seems what we are really missing here is the feature of the defunct kiofuse
(https://techbase.kde.org/Projects/KioFuse) which simply allowed to specify a
mount directory while using the great kio-fuse machinery.
Or being able to define another/several fio-fuse roots and use
https://github.com/KDE/kio-fuse/blob/master/utils/mount-url.sh with an option
to select the desired root.
That'd be a perfectly efficient solution, coupled with startup tasks.
Nice and sleek :)
For complete integration and user happiness, a simple (option in a relevant)
panel in system settings could allow defining the additional, stable kio-fuse
directory.
Other settings in the panel would allow defining the list of stable mount
points.
A contextual menu action could allow adding targets to the list from the file
browser.
In the meantime, Alberto's symlink solution may be leveraged with a bit FS
event monitoring, like watching apparition and disappearance of directories in
kio-fuse directory and making iwatch/fswatch manage the symlinks
automatically...
--
You are receiving this mail because:
You are watching all bug changes.
