Daniel, what is often helpful is to export the files to LaTeX and run that manually perusing the log files.
The tracking feature clashes with a few other packages, for example if I mark text with yellow background. I personally find it overrated in any case and try to avoid it. I use RCS for everything bigger than a short letter and comparing differences between versions in supported within LyX. greetings, el On 2020-02-26 12:44 , Daniel wrote: > On 2020-02-26 11:29, Daniel wrote: >> On 2020-02-26 07:29, Daniel wrote: >>> On 2020-02-25 21:45, Daniel wrote: [...] >> I got it to work after some battle. The endless typeset problem seem >> to have been caused by tracked changes within a TeX Code inset. I >> knew that using this combination was risky but I had no clue it could >> lead to a case where I don't even get an error message. >> >> I'll try to create a minimal example. Maybe it's worth knowing how >> this can happen. >> >> Daniel > > Okay, here it is I think. Whether the LaTeX code is typeset within > LyX or not does not matter, so it seems that the code generated by LyX > is the problem. > > As I said, I knew that putting tracked changed into a TeX Code inset > is asking for trouble. However, I just missed this one when copy and > pasting a whole passage with tracked changed enabled. > > Still it surprises me that there is no error message or anything. > Maybe a problem with the error handling in the booktabs package? > > Daniel > -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
