On Tue, Jun 17, 2025 at 10:40:18AM +0200, Pavel Sanda wrote: > On Tue, Jun 17, 2025 at 09:56:47AM +0200, Scott Kostyshak wrote: > > I recently ran into an issue [1] where one of my labels did not get > > defined properly and so the reference did not work. But I didn't realize > > it because LaTeX cannot easily give an error in this case, I think > > because it doesn't know if it's the last compilation. > > > > Would this be a nice feature for LyX to handle? That is, LyX can (and I > > think we already do) parse the final log. For example, we turn warnings > > about missing characters into errors, if I remember correctly. Can we > > also turn warnings about missing cross-references into errors by parsing > > the log? > > We are already parsing latex log for missing citations and broken references, > see bf99ece7366ad47945. If something does not work the best is perhaps to > send particular example so that we see what in the log was missed.
Thanks, Pavel. Attached is an example. The log entry is: LaTeX Warning: Reference `enu.blah' on page 1 undefined on input line 13. Does LyX catch it for you? If so, what is the warning in your log? Scott
missing-reference.24.lyx
Description: application/lyx
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org https://lists.lyx.org/mailman/listinfo/lyx-devel
