Input line is not correctly parsed for some compiler warnings (e.g. undefined references) #3150
Unanswered
Sebastian-Maier
asked this question in
Q&A
Replies: 3 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
-
And please provide a minimal example to reproduce the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
Latex Warnings like "Reference 'XYZ' on page 8 undefined on input line 275." are currently not parsed in a way that also extracts the corresponding input line from the compiler output/log. Therefore, there is no easy way to navigate to the line that caused the warning by clicking on the warning. (I am unsure whether this is a bug or intended/limitation.)
Describe the solution you'd like
Parsing warnings like these in a fashion that also extracts the input line (for easy navigation).
Describe alternatives you've considered
I tried different latex variants (besides lualatex) and different build tools/configurations (Makefile, latexmk).
Additional context
Typically, I use lualatex and a custom Makefile for the building of the PDF. I am using macOS. Other errors/warnings (like "Float to large by X.Ypt.") seem to be parsed just fine (and they also include the line number for direct navigation to the corresponding input line).
Beta Was this translation helpful? Give feedback.
All reactions