D10990: Add "Open symlink destination folder" into symlink's context menu
Mark Gaiser
noreply at phabricator.kde.org
Sat Mar 3 14:13:28 GMT 2018
markg added a comment.
In D10990#217446 <https://phabricator.kde.org/D10990#217446>, @rominf wrote:
> In D10990#217438 <https://phabricator.kde.org/D10990#217438>, @markg wrote:
>
> > I'm not so sure if this is a feature worth having.
> > Dolphin also works under windows, it doesn't know symlinks (something like it, yes, but it's not a symlink as it is under linux).
> >
> > Also, is it worth exposing that technical detail (symlink is quite technical) to the user?
> > Is a good solid reason for having this? Or would this just satisfy a edge case used by very few people (if ever)?
>
>
> Suppose I have file `A` and symlink `B -> A`. I want to copy file `A` to the FAT formatted flash drive using symlink `B`. I get an error because FAT doesn't support symlinks. Ooops... Leaked abstraction.
In that case (and always imho) the symlinks should be followed.
In your example, it should copy A.
But on the other side, you might sometimes want to copy symlinks as well.. Now you're getting into tricky details.
From a user friendly perspective i'd say that symlinks should always be followed thus A would be copied if you copy B.
We need more opinions on this one.
REPOSITORY
R318 Dolphin
REVISION DETAIL
https://phabricator.kde.org/D10990
To: rominf, #dolphin
Cc: ngraham, elvisangelaccio, markg, #dolphin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20180303/cb33d272/attachment.htm>
More information about the kfm-devel
mailing list