I am working on a multi-file document in LyX (my thesis) and occasionally have problems where LyX seems to rely on old version of intermediate files when updating the PDF output. Is there an easy way to force a clean/refresh from scratch within LyX?
For example, I have a separate LyX file that uses exclusively raw LaTeX (in ERT mode) to define acronyms that are shared across chapters. I then conditionally include this file in each chapter to enable building stand-alone chapters for review. The problem is that when I make and save changes (e.g. spelling) to an existing entry in the acronym file, the changes do not automatically show up in the PDF output on the next view "Update" (Shift–⌘–R) or if the PDF preview is build with "View" (⌘–R). As a work around, I have forced a refresh by adding a new dummy entry to the acronym list, which apparently forces LyX to rebuild the temp files in a different way.
I have experienced similar issues with other non-plain text edits.
Any ideas of how to force a complete temp file re-build when updating the view?
I am aware of the low-level (La)TeX answers from this post but am looking for a LyX specific method, ideally one available through the graphical interface.
Environment:
LyX 2.0.4,
pdfLatex,
Mac OSX 10.7.4
Best Answer
Based on an informal discussion entitled "how to update
.aux
file in LyX?" (with the current "stable branch maintainer", Jürgen Spitzmüller) it seems that LyX automatically reruns a file based on an evaluation of the.log
file. Another motivation for this stems from the LyX documentation on Customizations (under the menu item Help > Customizations, section 5 Installing New Document Classes, Layouts, and Templates):For example, the default LaTeX warning message
would initiate a re-compile, while the
etaremune
-specific warning messagewas "a specific syntax" that needed to be considered. Another example from the
totcount
package:that is not referenced as a "LaTeX warning", but rather a "package warning". Moreover, there seems to be no interest in implementing a forced, full, recompile (more than once) option in LyX. So, if the change does not initiate "a known warning", no recompile will be performed.
A suggestion would be to post this, in the form of a full example of your document usage/structure that shows the validity of such an option as being a feature, on the LyX mailing list. See their Get involved or Mailing Lists page for a reference.