>
> But the only one for truly consistent behaviour. If you want to export
> stand-alone, uncheck the master setting.
>

Even if the master setting is not set in the child, LyX still display all
macros perfectly if the master document is open.
My complaint is this: if LyX is able to interpret things and display them in
the editor, it should be able to generate the output. That's all.
Specially if this problem is not present in older versions.

No, you can *include* the sub-documents and use the includeonly feature
> to compile a subset of sub-documents where LaTeX will ensure
> (almost) correct page numbers and references and LyX will use the
> parent doc settings instead of the child-doc ones.
>

What happens when you set the include only option?
The whole document is generated and the pages are ommited or it handle the
pages in a more fashioned way?

I am asking this because, if LyX handles it in a good way, we can change the
action of the view button of child docs to automatically generate the master
document including only the active document. This appears suitable for me
and is better than blocking.


> Actually, *you* generate the error -- a reference to a label that does
> not exist in the document. Setting a master (currently) is just an
> "editing hint" but does not change the way a document is compiled
> stand-alone.
>

If LyX options were consistent, it won't let me generate such errors.
It doesn't really matter if I am responsible for them or not: computers are
here to handle problems we don't want to deal with, right? They are not here
to introduce another class of problems (although I agree this is not always
true :-) .


> I am not sure about this. If I remember right, the LaTeX run is done in
> nonstopmode but the output not opened in a viewer -> I'd like a
> "show output anyway" button in the error message dialogue. Having
> a look at the output is sometimes far more helpful than TeX error
> messages.
>

A "show output anyway" button would be great.
However, if LyX consistency were assured, there's no need for it (expect
when using ERT).

---
Diego Queiroz

Reply via email to