From: Justin C. W. <ju...@ma...> - 2008-10-27 00:00:39
|
Hi, Alex, On Oct 26, 2008, at 15:51 , Alex Hamann wrote: >> 2) Next, a preview glitch: I have 537 entries in my .bib file. If I >> select them all, a preview is generated in the "integrated" preview >> window, without fuss. However, if I have the floating preview window >> open, it shows a TeX error (the integrated window still makes no >> complaint). The TeX log shows no errors (a bunch of TeX warnings >> about under/overfill, and bibtex warnings about missing fields, but >> no >> errors). I tried a binary search to see where the problem might be, >> but the results were a bit perplexing. >> >> If I isolate 463 of the 537 items in a static group, I always get the >> error. Depending on the selections making up the group, the error >> goes away after deselecting some small number of items (1, 2, 3, ..). >> >> I hope that's clear; it seems pretty weird to me. > > What I did today in order to track down items which contain a TeX > error (which seems to be your problem as well) in a bib file with > > 700 > items was to switch the bottom frame of the main window to TeX > preview. > Then I selected a number of items at the same time and tried to track > down which items cause the errors. It is a pain in the neck to have > to do that for large bib files but there is probably little one can > do (besides maybe selecting all items in the main window, then > pressing > the TeX preview-icon and switch to the Log report to see where > problems > occur - but on my old and slow iBook that is even slower than the > other > approach). The way I got to the above was essentially a binary search. This got me the "463" number, which so far seems magic for this problem. Note that the "TeX error" does *not* show up on the "integrated" preview panel, only on the external (SHFT-CMD-T) panel. As Adam suggested, this may be related to the task stuff (in an earlier problem I was seeing with previews, the behavior was different between the two, which (I assume) made Adam think of this issue). AFAICT, this problem is not a TeX "processing" problem; perhaps a TeX "operation" problem, or an interaction between TeX and BibDesk. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds -------- If you're not confused, You're not paying attention -------- |