https://bugs.kde.org/show_bug.cgi?id=465646
--- Comment #10 from David Faure <fa...@kde.org> --- Well done for this investigation. I think it's all about whether the modification time of the directory gets updated (which is the case when creating a temporary file, but not when overwriting the desktop file directly). Note that most KDE software creates a temporary file via QSaveFile when saving too, not just the swp file (this is in order to rename the file atomically at the end of the write, to avoid losing everything if the partition is full). But clearly nano doesn't do that... Code pointer: KSycocaPrivate::needsRebuild() in kservice calls checkDirectoriesTimestamp which looks at the timestamp of directories (and compares them with the time in the database header, coming from readSycocaHeader()). We could look at the timestamp of every single file, but this feels quite slow, for a rare "editing with a broken command line tool" scenario... (broken because it would lose everything if the partition is full) -- You are receiving this mail because: You are watching all bug changes.
