Use latexmk to filter the log file

Question

I am usually using latexmk in a split shell with my code on the left and latexmk in -pvc mode on the right.

When using some packages which themselves load a lot of other packages (think beamer) the log file contains tens or even hundreds of lines of messages from the packages being loaded (also spelling files, fonts, etc.).

I would like to prune the output to just the warnings, the errors, and latexmk’s own messages so these do not get lost.

Any ideas?

Answer 1

You can use pplatex to filter errors, warnings and badboxes: http://www.stefant.org/web/projects/software/pplatex.html

(the compilation of http://dl.dropbox.com/u/12697903/pplatex/pplatex-1.0-rc1-src.tar.gz needs an additional #include in src/outputfilter.cpp)

If you then have ppdflatex in the path, you can create a ~/.latexmkrc file like the following to have a great workflow (with KDE, but it should be easily adaptable):

$pdf_mode = 1;
$pdflatex = 'ppdflatex -- -interaction=nonstopmode -shell-escape -synctex=1';
$pdf_previewer = "start okular";
$pdf_update_method = 0;
$recorder = 1;
$preview_continuous_mode = 1;
$sleep_time = 1;

Answer 2

I just remembered that rubber has log filtering. It turns out there is a program in the rubber package called rubber-info which is solely for parsing the log file.

Because latexmk acts as tee (writing the to the logfile and printing to stdout and stderr, we can run rubber-info after latexmk is finished.

So I put this in a shell script:

#! /bin/bash

latexmk --pdf $1 > /dev/null 2>&1
rubber-info --check $1
rubber-info --boxes $1

and set makeprg in vim to

:set makeprg=latexmake\ %:h

And now I have only the errors and warnings (including overfull boxes).

Answer 3

Try the silence package, it can filter a variety of errors, warnings, and messages.

Answer 4

You need to write a small script which filters the log file. Either a Perl, Python or similar scripting language of you choice or a longer egrep line (if you under a *nix system) should do it.

Before I knew latexmk I wrote my own minimalistic version of it (actually of texify) which does such filtering. Here the filter code on its own as an example. It is a Perl script which still needs adjustments to include latexmk's own messages.

#!/usr/bin/env perl
use strict;
use warnings;
my $nobox = 0; # Should box warning be excluded
my $nextlines = 0;
while (<>) {
    if ($nextlines > 0) { $nextlines--; print STDERR $_; }
    elsif (/^(!\s+)?LaTeX (?:Warning|Error)/i) { print STDERR $_; }
    elsif (/^! Undefined control sequence\./i) { chomp; print STDERR $_, ": "; $nextlines = 1; }
    elsif (/^! Use of .* doesn't match its definition\./i) { print STDERR $_; $nextlines = 3; }
    elsif (/^!/i) { print STDERR $_; }
    elsif (!$nobox && /(overfull|underfull|badbox)/i) { print STDERR $_; }
}

Answer 5

I asked a similar question a while back (but much after this question was originally asked) about filtering the log file with arara: Arara rule for log file scraping. While the details of the answer are arara specific, the underlying program used is texloganalyser. It should be possible to work that into whatever build system you are using.

Answer 6

If you don't edit your preamble very often, you can also precompile it, it will also make you gain time with each compilation.

You can find details in this page, but essentially, you have to

• separate the fixed preamble from the document, paste it into a file named preamble.tex

• run latex -ini -job-name="main" "&latex preamble.tex\dump" or if you prefer pdflatex run pdflatex -ini -job-name="main" "&latex preamble.tex\dump"

• add %&main.fmt at the beginning of your file and remove \input{preamble}

• add -parse-first-line to latex/pdflatex's flags.

I believe you can add a latexmk rule to recompile the preamble if you edit it, also.

Answer 7

Though it would miss TeX warnings, showing only LaTeX ones, you could patch LaTeX's error and warning commands to write the warnings and errors additionally to another separate log file. This log file would then only contain errors and warnings. Latexmk could then cat this file at the end of the run.

I would be willing to have a go at this if anyone thinks it useful, but at the moment I think the missing of TeX's messages would be a deal-breaker. Perhaps if using LuaTeX, one can hook into TeX's messages too?