https://bugs.kde.org/show_bug.cgi?id=432627
imba...@gmail.com changed:
What|Removed |Added
CC||imba...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=432627
Andrew Gunnerson changed:
What|Removed |Added
CC||accounts+...@chiller3.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=432627
prettyvani...@posteo.at changed:
What|Removed |Added
CC||prettyvani...@posteo.at
--
You are
https://bugs.kde.org/show_bug.cgi?id=432627
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--
You are
https://bugs.kde.org/show_bug.cgi?id=432627
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=432627
Dashon changed:
What|Removed |Added
CC||dashonww...@pm.me
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=432627
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=432627
Bharadwaj Raju changed:
What|Removed |Added
CC||bharadwaj.raju777@protonmai
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #8 from Nate Graham ---
(In reply to Jason Straight from comment #7)
> Okay, thanks for that explanation. So, should we file reports when we find
> apps that don't work with opening (double or right click), and drag and
> drop, or not?
Yes
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #7 from Jason Straight ---
Okay, thanks for that explanation. So, should we file reports when we find apps
that don't work with opening (double or right click), and drag and drop, or
not?
I'm certainly glad that the changes we've seen in
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #6 from Nate Graham ---
The gist of your question is "why don't we always use kio-fuse and local paths
instead of sometimes using native KIO stuff with URLs?". The answer is because
native KIO operations are faster and asynchronous. They
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #5 from Jason Straight ---
s/vnc/vlc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #4 from Jason Straight ---
Sorry. I know you shouldn't have to educate me, but if all those apps can take
file paths, how do they break?
Even with VLC accepting smb:// urls doesn't that cause problems when the share
it's trying to access
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #3 from Nate Graham ---
Then we break apps that do support and expect smb:// URLs, which would include
not only all KDE apps, but also some 3rd-party ones that can be configured with
internal Samba clients, such as VLC.
--
You are
https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #2 from Jason Straight ---
Why not just use the fuse path for everything smb related, if fuse is supported
on the host system?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432627
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC|
16 matches
Mail list logo
