You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To debug errors, it would be handy to display in which line the error occurred. Since the editor is merging a figure with its template, the line numbers displayed in the editor are off.
Example: In a template the marker <> is at line 40, but the error is in line 2 of the edited file, so LaTeX displays an error in l.41.
Not sure how easy it is to fake the line number in KatePart, though.
Bonus: Its probably also possible to parse the log and highlight the line in question. :-)
The text was updated successfully, but these errors were encountered:
To be honest, I've never looked at the line number in the log output, I wasn't even aware that it includes a line number.
I looked at the KatePart API, it does not seem to provide a feature to change the line numbers, only to show/hide them... So the option with parsing the log and highlighting the line seems more realistic (there is an API to mark lines).
I would be happy to merge a pull request if you want to implement that, not sure when I find time to look into that.
To debug errors, it would be handy to display in which line the error occurred. Since the editor is merging a figure with its template, the line numbers displayed in the editor are off.
Example: In a template the marker
<>
is at line 40, but the error is in line 2 of the edited file, so LaTeX displays an error inl.41
.Not sure how easy it is to fake the line number in KatePart, though.
Bonus: Its probably also possible to parse the log and highlight the line in question. :-)
The text was updated successfully, but these errors were encountered: