Jeff King <peff@xxxxxxxx> writes: > My latex usage is all from a past life, so I didn't even try out your > tool. But I did wonder what your rationale was in making a separate > command as opposed to providing a script that could be plugged in as an > external diff. My LaTeX documents are usually sets of .tex files including each other, plus figures and possibly Makefiles. So, git-latexdiff does a full checkout of the old and new tree, then runs latexdiff on the main file, and then compiles the result. A diff driver would work well for a standalone file, but I don't think you can plug it in this kind of situation. Also, git-latexdiff has a few hacks like detecting the main latex file automatically by grepping all .tex files for "documentclass", detecting the presence of a Makefile to compile the document, ... that would hardly fit in a diff driver. That said, that may be just me not knowing diff drivers or difftools well enough. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html