[dolphin] [Bug 464585] Visually mark hardlinks

Jörg bugzilla_noreply at kde.org
Tue Sep 9 14:42:23 BST 2025


https://bugs.kde.org/show_bug.cgi?id=464585

Jörg <jorg_heuer at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jorg_heuer at gmx.de

--- Comment #7 from Jörg <jorg_heuer at gmx.de> ---
(In reply to lowell.bv from comment #2)
> Summery:
> - Add a visual mark to distinguish a hard-link from a normal file. 
...
> Suggested behaviour: 
> - Visually mark any file whose hard-link number is greater than one. 
>     - Mark the corner of the file as done with symlinks.
A little red arrow as used under Windows by Linksshellextention would be fine. 
(  see  https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html )
..
> Use-case:
...
>     - A user may want to make a local change, but the file is hard-linked so
> it may apply the change globally
THIS is the most important reason. Hardlink are good at saving space  and add
*clarity*, if one file was used in number of processes /
submissions/dokumentations. But you need a warning  to point you to generat a
new version.
 - A user may falsely believe that a file is hard-linked due to a prior  move
instead af a generating a hardlink

> Conclusion:
> Though the use cases may be considered niche, there are benefits in being
> able to see at a glance if a file is hard-link or not. This feature would
> greatly improve the user output that dolphin provides, enabling the user to
> take the correct action. Currently proper hard-link support is practically
> nonexistent on file browsers, which makes this feature tedious to use at
> best, difficult to use or invisible at worst.
I am a new user and was shocked that dolphin don't support this filesystem
feachure I had use even in UNIX Sytem V. I don't want to use Windows for my
docment managment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list