--- Comment #11 from Michał Dybczak <michal.dybc...@gmail.com> ---
(In reply to Albert Vaca from comment #10)
> There is no way to surface this error to the user in a backwards compatible
> way :( It might be seen as a bug, but I think it's way better than just
> succeed with a corrupted file.
I agree. But error message comes with a message, right? Why not create some
condensed, smart message that will shed some light?
Like for example: "Error, faulty sshfs version detected (3.0 and 3.2)"
Yeah, I know, it's also bad way to show it. But maybe with some brainstorming,
it will be possible to design error message in a more informative manner?
"Error, sshfs version 3.0 and 3.2 are not supported."
It's still cryptic but at least it looks like a design and not a bug. Or maybe
"Error, sshfs version 3.0 and 3.2 are not supported due to a serious transfer
This is bolder and less eloquent message but I'm not sure how shorter this
could be explained.
Of course, that's just my proposition and I trust KDE Connect development team
will choose the best solution or wording of that message. Maybe use some words
that allow users find easier the info about that sshfs bugs?
You are receiving this mail because:
You are watching all bug changes.