[dolphin] [Bug 464585] Visually mark hardlinks
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Fri Feb 24 19:31:36 GMT 2023
https://bugs.kde.org/show_bug.cgi?id=464585
lowell.bv at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lowell.bv at gmail.com
--- Comment #2 from lowell.bv at gmail.com ---
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.
- Use an icon or the total number of hard-links.
- Format the file name to visually differentiate it form other files.
- Use semi-bold to indicate its a hard-link!
- Optionally use italicized for all link types.
Use-case:
- Allowing the user to easily know if the file is "hard-linked" elsewhere would
empower more intelligent decisions on how to interact with files.
- A user may want to free space on their disk, deleting a single copy of a
hard-linked file will not accomplish this
- A user may wrongly believe they have a second (hard-linked) copy of the
file elsewhere and want to delete the current copy
- A user may want to make a local change, but the file is hard-linked so it
may apply the change globally
- A user may falsely believe that a file is hard-linked but due to poor
application interaction said link was destroyed
- text editors with "backup" enabled often replace hard-linked files
with new copy of the text file destroying the hard-link
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list