Is there any chance you will add the "unified" format of Diff report often required by patch utilities?
According to Wikipedia:
The unified format (or unidiff) inherits the technical improvements made by the context format, but produces a smaller diff with old and new text presented immediately adjacent. Unified format is usually invoked using the "-u" command line option. This output is often used as input to the patch program. Many projects specifically request that "diffs" be submitted in the unified format, making unified diff format the most common format for exchange between software developers.
A service I use regularly requires patch files as produced by the following command line:
If you are unwilling to develop this specifically, how about a generic facility for external tools? I mean that you specify a name and command line in settings and then the name shows up on a special menu. When you select it, the command line is launched.
This needs special tokens for pasting in the left and right file paths as parameters on the command line. Most programs get this bit wrong: you need the ability to assemble the path from fragments so, for example, output paths can also be synthesized. I suggest the following:
$commonpath - The part of the path which is common to left and right files.
$leftpath - the rest of the path on the left, up to, but excluding the file name.
$rightpath - ditto for the right.
$leftname - the file name without extension on the left.
$rightname - ditto for the right.
$leftext - the file name extension on the left.
$rightext - ditto on the right.
Sorry to revive an old thread, but given ExamDiff Pro is one of the best diff programs, I always simply assumed I could view and parse Unified Diff files. After trying several times, I realized that EDP complains that it is an "Invalid session file."
Is there any way to parse .diff files using ExamDiff Pro, or must I use another solution such as TortoiseGitUDiff?