Hi John,
good question! Thinking that one of those characters might be the culprit I forgot to mention that compiling the child document alone _always_ works. But after saving and including it in the master document, compiling _always_ enters that loop (or whatever it is).
I can reproduce this behavior as many times as I want.
So, in the layman's thinking something on the way to include the child in the master is going wrong. The only difference is that sometimes the child file is destroyed and sometimes it is not. My master document in question has 14 child documents. Most contain glosses and other special things typical for linguistic theses and they include and compile just fine. Funny enough, only the child with characters as shown in the screen shot creates the problem. A pseudo problem? However, now it becomes clear to me that this most probably has nothing to do with any characters - very same examples do work well in other documents (document class KOMA-Script article, without master-child relationship).

You seem to be on the right track as to what is causing this mysterious problem - I hope so very much!
Miede's template?
I pray as I am very desperate after days of frustration!

Thanks and regards,
Michael Berger

On 02/14/2016 06:29 PM, John Kane wrote:
Yes does the one sub-file do the same thing if you compile it alone in the template ?

On 14 February 2016 at 12:13, <[email protected] <mailto:[email protected]>> wrote:

    On 2016-02-14 08:59, Michael Berger wrote:

        Hi all, can somebody help, please!

        I am working on a thesis (linguistic) based on Miede's
        classicthesis.v4.1.
        The Example per screenhot causes the compilation to PDF to run
        endlessly.
        I cannot interrupt the process and am forced to cut the power off.
        That makes it even worse - in most cases I am left with a
        spoiled file
        (0 bites).
        However, sometimes the file (a child document) remains intact
        and if I
        then remove the example the export to PDF succeeds as normal.
        All characters had been typed in using the keyboard.
        I want to add that none of those characters used in the
        Example poses
        a problem when typed in normal text or in a gloss as a single
        character.


    I can't tell you what's going on (aside from the fact that you've
    probably found a way to make TeX recurse or loop), but I'll bet
    that whoever _can_ tell you what's going on will want to see the
    Lyx file that causes the problem. Attach it, maybe?

    If the thing is huge or proprietary, try trimming your document
    down to the one offending equation.  That'll either provide a
    nice, compact Lyx file to distribute, or it won't cause the
    problem in the first place which will be usefully educational.




--
John Kane
Kingston ON Canada

Reply via email to