git ships a nice little tool to compare two different versions of the same textfile and highlight its differences: git difftool. It basically does two things for you. a) checkout the versions of the file to compare. b) fire up your diff program to show you/highlight the differences. This posts explains how git difftool can quickly be configured and how it's used.
In certain cases git-latexdiff might terminate with errors instead of producing a visual diff file. For example, it might struggle with broken latex code, broken figures, certain usage of subfiles, etc. In such cases, it might help to manually do what git-latexdiff would do fully automatically for you. This post is provides a simple step-by-step explanation of how you could achieve visual highlighting even with broken Latex files.
git latexdiff accounts for checking out the different version of a Latex file as well as comparing them with latexdiff in a single command: you only need to specify which latex file and versions should be used for the comparison.
In order to prevent possible tampering with code in git repositories you work with (e.g. malicious manipulation of objects during clone, fetch, push...), check if these lines exist in your ~/.gitconfig and add them, if they don't.
latexdiff is a useful tool to determine changes between different versions of latex files and highlight them in a pdf (similar to MS word does with tracking changes). latexdiff-git is a wrapper around latexdiff optimized for git (and mercurial, but we'll only look into git here). With it you can specify a latex document file … Continue reading latexdiff-git: highlight changes between revisions of latex files managed in git