Watch Document: Error Reporting and latexmk.log

[taiya]

Very often something goes wrong and all I get is this:

Could not find any messages containing line information.
Please take a look at the log file engage.latexmk.log to find the source of the problem.

It would be nice if in these situations the LatexWatch could just dump the log file directly in the window, no?

[sorbits]

As an intermediate step, the text could be made into a link (if this is not already the case).

Here’s a simple example of using JavaScript to open a file (from TextMate’s HTML output):

Open <tt><a href="#" onClick="javascript:TextMate.open('/etc/hosts')">/etc/hosts</a></tt>

[sanssecours]

It would be nice if in these situations the LatexWatch could just dump the log file directly in the window, no?

Do you mean that we should:

1. open the file filename.latexmk.log in a new tab in TextMate, or
2. display the content of the logfile in the Notification Window?

I do not think that either of this options is ideal. Especially option 2 seems kind of extreme. I think it would be better to just to improve the parser code to catch more helpful error messages. Hopefully I will have time to update the parser code in the next weeks.

As an intermediate step, the text could be made into a link (if this is not already the case).

Thanks, for the tip Allan. But I think in the situation Andrea described only the Notification Window is open. As far as I know there is no (easy way) to add a link there…

[taiya]

I agree it's not ideal, but better than having to chase down the log file by hand.

A link would've been optimal!
Even better if errors where better caught but there is always room for things to go wrong!

Sent from my iPhone

On Jun 30, 2016, at 12:02, René Schwaiger [email protected] wrote:

It would be nice if in these situations the LatexWatch could just dump the log file directly in the window, no?

Do you mean that we should:

open the file filename.latexmk.log in a new tab in TextMate, or
display the content of the logfile in the Notification Window.
I do not think that either of this options is ideal. Especially option 2 seems kind of extreme. I think it would be better to just to improve the parser code to catch more helpful error messages. Hopefully I will have time to update the parser code in the next weeks.

As an intermediate step, the text could be made into a link (if this is not already the case).

Thanks, for the tip Allan. But I think in the situation Andrea described only the Notification Window is open. As far as I know there is no (easy way) to add a link there…

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.