https://bugs.kde.org/show_bug.cgi?id=435294
--- Comment #9 from Oded Arbel <o...@geek.co.il> --- (In reply to tagwerk19 from comment #8) > (In reply to Oded Arbel from comment #7) > > Baloo doesn't deal in inodes - it only cares about file paths, so unlikely > > any shenanigans with inodes will cause baloo to misbehave. > Let's say "I'm not sure about that" ... > Baloo deals with file renamings so has to "know" inodes - or some other > invariant. I'm pretty sure about it. Baloo uses inotify (https://man7.org/linux/man-pages/man7/inotify.7.html) to track file system events. inotify sends notification about rename events, that includes the original path text and the new path text. inotify may handle inodes internally, but it does not expose that information to user-space application - including Baloo. Here is the relevant code: https://invent.kde.org/frameworks/baloo/-/blob/master/src/file/kinotify.h -- You are receiving this mail because: You are watching all bug changes.
