As detailed in another thread, I struggled trying to pin down the source of a weird biblatex related error in a big document I am working on. The doc itself is composed of a master document and numerous child documents, one per chapter.
My strategy was to duplicate the master file, then start bisecting until I narrowed it down to one chapter, then bisect on the chapter until I got it down to the wrong line, etc. Given that each compilation takes several minutes, I spent my whole morning doing this. Nonetheless, I eventually tracked the error down to a typo in a reference. as reported elsewhere. Once I found the error, I set restoring the original setup. This is where the weirdness started to happen. I did the following: 1. Fixed the reference 2. Tried to compile the original document 3. Failed with the same error! This was strange. Perhaps there were two unrelated errors, and my bisecting had failed? I recreated the error in the ref, repeated, with variations, the same bisecting steps as above (count another 2 hours), and reached the same result. No other errors were present. Yet, I repeated steps 1-2 above and got the same result, compilation still failed. So I tried this: 4. Save the original master doc with a new name (as before) 5. Try to compile the newly created file **without touching it in any way** 6. Compilation succeeds! 7. Try to compile the identical, original master file 8. Compilation fails Weird. Perhaps LyX caches some intermediate files (bbl and bcf) , I thought, in its tempdirs (/tmp/lyx... etc). So I quit lyx, manually erased LyX's directory in /tmp, restarted lyx and tried again steps 4-8. I got the same results. I even thought saving a file with a new name would introduce some slight alteration in its content. Nope. diff confirms the files are byte-identical. Yet one fails and the other succeeds. I have no idea what is going on. The only logical answer, in my mind, is that there are some cached results still lying somewhere. But where? Cheers, Stefano -- __________________________________________________ Stefano Franchi [email protected] <[email protected]> http://stefano.cleinias.org
