https://bugs.kde.org/show_bug.cgi?id=398446
--- Comment #5 from a.saout...@gmail.com --- I'm not entirely sure how much better that would be. They would then have to navigate all the way back to what they want. Usually a CIFS mount will be tied to just one share. But to get to a KIOFuse samba share, for example, the path would be / -> smb -> user@server -> (insert share folders and files here). Itself, / might do a dirlist with all sorts of slaves already mounted (mtp, sftp, smb, fish etc...), potentially confusing the user. More importantly , where would the patches be though. Do you only want them in KDE dialogs? Do we want GTK dialogs to display them. I know many apps that do their own thing altogether... Do you want each individual mount point in KIOFuse to show up as a separate item, or just the slave? One must also consider performance considerations. With the way the current KIO integration is done, the capability of KIO to cause blocking issues is reduced as much as can be. Even introducing KIOFuse into the places panel I believe can cause issues if it lags hard or deadlocks. In a typical scenario of opening files via Dolphin the only extra command needed is a KIO::stat -> KIO::get. We try to limit browsing inside a mount as much as possible. Allowing an easy way to do so can cause all sorts of issues. Some slaves have a substandard KIO::listDir implementation (MTP being an obvious culprit), and God forbid a user enables previews in a KIOFuse mount. One workaround I can think of, at least in open/save dialogs, is to force redirect to the remote URL if a KIOFuse mount is entered (as is done in https://phabricator.kde.org/D28290). -- You are receiving this mail because: You are watching all bug changes.
