do you use non-ascii chars in the file names?
On 08/26/2011 01:58 PM, Weng Xuetian wrote: > Yes, I already knew that from bugzilla, and I have patch strigi by > hand to avoid index fails (only do full text index and add "C++ > language fields")..... Actually index for my C/C++ already works and I > can search them via content or filename, seem it works just like in > 4.6. > > (Sorry for forgetting send to maillist..) > > On Fri, Aug 26, 2011 at 7:53 PM, Sebastian Trüg <[email protected]> wrote: >> then it might simply be that your source files are never indexed because >> indexing fails and each time the folder changes it tries again. >> >> Indexing source code currently fails due to strict data integrity checks >> in Nepomuk which were not there in 4.6. Strigi does not create valid >> data in all cases yet. source files is one of these cases which I just >> fixed in git master. The next version of Strigi will thus fix indexing >> of source files. >> >> Cheers, >> Sebastian >> >> On 08/26/2011 01:42 PM, Weng Xuetian wrote: >>> Chakra and KDE 4.7. >>> >>> On Fri, Aug 26, 2011 at 7:39 PM, Sebastian Trüg <[email protected]> wrote: >>>> which version of kde is this? >>>> >>>> On 08/26/2011 12:14 PM, Weng Xuetian wrote: >>>>> But seems nepomukindexer are running via ksysguard... >>>>> >>>>> And one of my very large source folder (which doesn't changes) get >>>>> fully rescaned (notice this via nepomukcontroller), but I don't know >>>>> the reason or what cause this. So I wonder there is a bug... >>>>> >>>>> The situation is like this >>>>> Develop/a <- large source folder, never changed these days >>>>> Develop/b <- smaller one get develop and compiled. frequently. >>>>> >>>>> ...But why "a" get rescaned I have no idea... So I even don't know how >>>>> to describe this bug... >>>>> >>>>> And another annoying bug happens here... >>>>> https://bugs.kde.org/show_bug.cgi?id=279351 >>>>> >>>>> On Fri, Aug 26, 2011 at 5:31 PM, Sebastian Trüg <[email protected]> wrote: >>>>>> it is used and only changed files are re-indexed. >>>>>> In 4.7 only the single changed file is updated. in previous versions the >>>>>> whole folder is updated. Here "updated" means that the mtime is compared >>>>>> for each file in the folder and if that changed the file is re-indexed. >>>>>> >>>>>> On 08/26/2011 05:31 AM, Weng Xuetian wrote: >>>>>>> Hi, >>>>>>> Nepomuk sometimes will try to reindex the files under a directory due >>>>>>> to a >>>>>>> single file change (I notice you guys are having plan to avoid scan >>>>>>> unchanged >>>>>>> files), but it seems nepomuk never uses the file modify time to check >>>>>>> whether >>>>>>> the file is changed or not. If it was used, I think thousands of >>>>>>> reindexing >>>>>>> events can be avoid on my laptop. >>>>>>> >>>>>>> Do nepomuk really use it? If not, is there any reason for not using >>>>>>> this? I >>>>>>> see nepomuk already stores the index creation time in KDE 4.7 (Wwhich >>>>>>> shouldn't be display on info panel by default and the displayed time >>>>>>> seems to >>>>>>> use the wrong timezone), I think a simple compare will avoid most of >>>>>>> reindex >>>>>>> on my disk. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Nepomuk mailing list >>>>>>> [email protected] >>>>>>> https://mail.kde.org/mailman/listinfo/nepomuk >>>>>> _______________________________________________ >>>>>> Nepomuk mailing list >>>>>> [email protected] >>>>>> https://mail.kde.org/mailman/listinfo/nepomuk >>>>>> >>>>> >>>> >>> >> > _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
