On 05/10/2011 09:09 AM, Guenter Milde wrote: > On 2011-05-10, Jürgen Spitzmüller wrote: >> Guenter Milde wrote: >>> For truly consistent behaviour, we would have to disable stand-alone >>> compilation of documents setting a master (except for "included" (vs. >>> "input") documents). >> Why this? I have many documents with a master set that get compiled stand- >> alone from time to time and should _not_ inherit anything from the master >> then. > Because the OP complained that it is incosistent to show math-macro > expansions in the child doc but not make them available in stand-alone > compilation. > > The same argument would hold for references to sections, equations, > tables and figures in other parts of the document. > > Actually, I regularly compile stand-alone child docs (to save time on > checking the appearance in the output). I have set up a "stand-alone" > branch for math-macros and bibliography and I can live with the > question marks in the references. > > The above was just stating the "pure" solution to the OPs report. > However, I vote to keep things as-is, because: "practicality beats > purity". > > Just make it very clear in the documentation that parent-document > features are non-available in the child if compiled stand-alone (without > include feature) even if rendered in the LyX window - this is a feature. > We did establish that this is a change from 1.6.x, where parent macros are written to the child. That was not intentional, and the behavior depends upon the setting of EXPORT_IN_THREAD. We can keep it as it is, but then we should make it consistent (and could remove useless code).
Richard
