[Active] [Bug 316158] New files are not being indexed until after reboot
https://bugs.kde.org/show_bug.cgi?id=316158 --- Comment #4 from Thomas Pfeiffer --- I can confirm that this is fixed. Yay! -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 316158] New files are not being indexed until after reboot
https://bugs.kde.org/show_bug.cgi?id=316158 Marco Martin changed: What|Removed |Added Latest Commit|http://commits.kde.org/nepo |http://commits.kde.org/nepo |muk-core/0b5a17ee52780fdf2e |muk-core/ba02058c7efe6c4ace |49f82ad0c541052d8ff0a5 |f3b3b2aef55de0afd7aaef --- Comment #3 from Marco Martin --- Git commit ba02058c7efe6c4acef3b3b2aef55de0afd7aaef by Marco Martin. Committed on 11/04/2013 at 21:27. Pushed by mart into branch 'KDE/4.10'. consider "old" files when a file that has a very old modification time is copied in an indexed folder, checking the modification time isn't enough. we have to check the modification time of the folder *and* of the file, then index the file if any of them is recent. in this case it catches both the cases an already existing file has been modified or the case when an "old" file gets copied there (in that case is the directory modification time that catches it) M +4-2services/filewatch/nepomukfilewatch.cpp http://commits.kde.org/nepomuk-core/ba02058c7efe6c4acef3b3b2aef55de0afd7aaef -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 316158] New files are not being indexed until after reboot
https://bugs.kde.org/show_bug.cgi?id=316158 Marco Martin changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/nepo ||muk-core/0b5a17ee52780fdf2e ||49f82ad0c541052d8ff0a5 --- Comment #2 from Marco Martin --- Git commit 0b5a17ee52780fdf2e49f82ad0c541052d8ff0a5 by Marco Martin. Committed on 11/04/2013 at 21:27. Pushed by mart into branch 'master'. consider "old" files when a file that has a very old modification time is copied in an indexed folder, checking the modification time isn't enough. we have to check the modification time of the folder *and* of the file, then index the file if any of them is recent. in this case it catches both the cases an already existing file has been modified or the case when an "old" file gets copied there (in that case is the directory modification time that catches it) M +4-2services/filewatch/nepomukfilewatch.cpp http://commits.kde.org/nepomuk-core/0b5a17ee52780fdf2e49f82ad0c541052d8ff0a5 -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 316158] New files are not being indexed until after reboot
https://bugs.kde.org/show_bug.cgi?id=316158 --- Comment #1 from Thomas Pfeiffer --- File indexing is not triggered by newly added files. De- and reactivating the indexer from Desktop Search settings does trigger indexing, though. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
