-
The current nightly uses an unlimited number of search terms, so you can easily check whether this is your problem.
2010-01-07 10:20:24 UTC by hofman
-
Andreas, please send me that PDF file or a download link to it. This is separate from the alias/symlink issue, but I'd like to check it out. For full-text indexing, Spotlight and Search Kit should show the same results...
OK, I just checked the code, and I didn't realize the maximum number of terms was still limited. I'm using this option set in my own code, and have no problems with...
2010-01-06 19:33:26 UTC by amaxwell
-
Adam, I believe you are right with the two issues: I followed your test recommendation and created a new bib file and added a record, which has the large pdf in question linked to (by symbolic link, not alias). I also tried to drag/drop the pdf to the record. BD shows file indexing or index verification message and once finished does NOT find my name in that file (it occurs there actually 5...
2010-01-06 18:53:17 UTC by afischlin
-
That seems to have no relation to the original post (unless it uses an alias, in which case it's been answered). There can be many reasons why Spotlight is not always consistent with our indexing, we use some options, Spotlight may use other options (e.g. the max number of search terms, which is likely to make a difference for large files) and Spotlight seems to have a workaround for the alias...
2010-01-06 18:10:38 UTC by hofman
-
Andreas' first followup point says after quit/relaunch (which is as effective as reopening the file) some content cannot be found. I'd like to know if this is due to Search Kit indexing vs. Spotlight, or somehow related to updating the db.
2010-01-06 17:34:47 UTC by amaxwell
-
Adam, I did address both issues. The other issue is that if you change a file on disk (s.a. replacing an alias by a symlink, but that does not matter) WITHOUT notifying BD (reopen the .bib or replace the linked file in BD), the search index won't be updated. Your test case works correctly, so there's no bug there. Saving the file is totally irrelevant.
2010-01-06 16:55:45 UTC by hofman
-
Andreas, it sounds like you have two separate problems here, and Christiaan has addressed the alias issue. However, if you can reproduce the behavior of not finding your name in a pdf file that is /not/ linked via an alias, that would be useful for testing. Create a new .bib file, attach that pdf to an entry, save the .bib file, and then try searching by content. If that fails, there's a bug...
2010-01-06 16:30:56 UTC by amaxwell
-
What you say is completely consistent with the way it is supposed to work and what I say (I did exactly the same thing, except that I reopened the .bib file). It does not matter whether you replace and/or change a symlink and/or alias. Whatever you do ON DISK is not noticed by BibDesk (as far as the index is concerned), BD can NOT track the files. Therefore you have to change something in...
2010-01-06 16:21:36 UTC by hofman
-
I have overwritten an alias (Apple alias) with a symbolic link (via AppleScript) both pointing to the very same physical pdf, then saved the bibliography and BibDesk did NOT detect the change. I have NOT merely replaced a symbolic link with another one, possibly pointing to another file or whatever you did in your testing. I have in all my testing never touched the original pdf file, i.e. I have...
2010-01-06 13:39:14 UTC by afischlin
-
I think it depends on how you replace the alias by a symlink. If you replace the linked file in BibDesk by another (symlink) file, BibDesk notices and file content search works (I just checked that). If you just replace the file on disk, BibDesk won't notice until you reopen the .bib file. That's not a bug, it's not possible to track all the files on disk. But note that you don't need to quit BD,
2010-01-06 13:03:20 UTC by hofman
