https://bugs.kde.org/show_bug.cgi?id=328709
--- Comment #23 from Marcus Sundman <sund...@iki.fi> --- (In reply to David Edmundson from comment #21) > This would open up an absolutely massive can of worms. > ... > I'm sure everyone who is here saying they want this feature understands that > and knows why, but we have to find a way to communicate that to people new > to hard links. That's impossible. That kind of babysitting does not belong here (if anywhere). If someone does not know how XYZ works then it's 100% their responsibility to deal with consequences of whatever happens when they use XYZ. If you absolutely must insist on babyproofing the whole environment then sure, put the functionality behind a setting, either in the UI or having to add it to some conf file by hand or whatever. (In reply to Pedro Alves from comment #22) > > "Edit a file in kwrite, you get two independent files now out of sync.". > > Why would this happen? Perhaps kwrite saves files by first creating a new file and then replacing the old with the new. That would override the hard-linked file with a separate instance. But this kind of problems arise regardless of what kind of link you have, so that's not a valid argument. If someone assumes a program follows some specific link traversal policy then that's on them. This is the case with all programs and all kinds of links, and is unavoidable, and giving up the possibility of creating any kind of links is too high a cost for avoiding this category of problems. -- You are receiving this mail because: You are watching all bug changes.
