On May 14, 2014, at 8:19, Jeremy Van Cleve wrote:
> I'll definitely send in a bug report next time it crashes :-)
>
> Looking at the help
> (http://bibdesk.sourceforge.net/manual/BibDesk%20Help_12.html#SEC40), I
> was under the impression that the index would get rebuilt every time I
> close and reopen the document, but now that I'm looking again, it does
> seem to be verifying the index after reopening rather than rebuilding.
>
The wording is not really correct here, I think. It is not fully rebuilt, only
checked and updated. Though it does mention that it is only slow the first
time, and faster later.
Christiaan
> I must have just not noticed this; definitely awesome!
>
> On 5/13/14, 10:20 PM, Adam R. Maxwell wrote:
>>
>> On May 13, 2014, at 18:02 , Jeremy Van Cleve <[email protected]> wrote:
>>
>>> Yes, certainly its faster after the initial index. However, with almost
>>> 7k references, BibDesk crashes occasionally and I get impatient with the
>>> indexing after restarting and go to the command line and use Spotlight.
>>
>> It should never crash! Have you filed a bug report and attached crash
>> logs? The number of references will only affect initial indexing time,
>> in theory, since the index is saved to disk. It would be great to look
>> at the crash logs and see what's going on.
>>
>> thanks,
>> Adam
> --
> Jeremy Van Cleve
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
