https://bugs.kde.org/show_bug.cgi?id=469134
Méven <me...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |me...@kde.org
--- Comment #6 from Méven <me...@kde.org> ---
(In reply to Jin Liu from comment #5)
> (In reply to Méven Car from comment #2)
> > I am asking myself how best to fix this.
> >
> > Because for a single symlink that makes sens the user would want the symlink
> > to be "duplicated" at destination.
> > But for a symlink inside a directory being copied (imagine some kind of
> > backup), that could be unexpected for that user and break his workflow.
> >
> > I guess we'd need some input, either when copying a symlink or when copying
> > a folder containing symlink(s).
>
> I think by principle of least surprise, we'd better have the same behavior
> as: (in the order of importance IMHO):
> 1. `cp' and `cp -r' command.
> 2. Gnome (Nautilus)
> 3. Windows (Explorer)
> IIRC, of the 3, only Windows copies link target.
Are you using Wayland btw ?
I dug into the code.
It is a regression in kcoreaddons 593d3343a30e842a2764faec86347510e8183f91
https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/212
--
You are receiving this mail because:
You are watching all bug changes.
