Command Line Parameters
You launch DeltaWalker Classic from the command line like this:
DeltaWalker [parameters] [-vmargs [Java VM arguments]]
The executable is named DeltaWalker on every platform. With a default installation, it is:
- macOS: inside the app bundle,
"/Applications/DeltaWalker Classic.app/Contents/MacOS/DeltaWalker" - Windows:
"C:\Program Files\Deltopia\DeltaWalker Classic\DeltaWalker.exe" - Linux:
DeltaWalkerin the DeltaWalker-Classic folder that you unpacked the archive into
If DeltaWalker Classic is already running, it opens the comparison you ask for in the running instance, and the command returns right away. Use -mi, described below, to start a separate instance instead.
Parameters
file or folder pathname/URI: The files or folders to compare. DeltaWalker Classic detects whether they are files or folders and opens a file or folder comparison accordingly:
- With two paths, the first one is the Reference and the second one the Modified resource of a two-way comparison.
- With three paths, DeltaWalker Classic opens a three-way comparison: the first path is the First Modified resource, the second the Second Modified, and the third the Reference (the ancestor). If you specify more than three paths, only the last three are used. Three-way comparison is part of the Pro and Oro editions; DeltaWalker Classic Free tells you so and opens a two-way comparison.
- Besides local paths, you can give the URI of a remote resource; see the URI Syntax Reference. Remote locations are not in DeltaWalker Classic Free.
Specify full, absolute paths rather than just names or relative paths, or tell DeltaWalker Classic the working directory with -pwd=, described below.
-pwd=: The working directory against which DeltaWalker Classic resolves relative paths. Use it to avoid specifying full paths for every resource, or when integrating with apps that pass resource names as relative paths.
-merged=: Meaningful only when merging in a three-way file comparison. SCMs that integrate an external merge tool specify a fourth file that receives the result of the merge; pass that file’s path with -merged=. When you save the Reference (the middle pane), DeltaWalker Classic writes it to that file.
-mi: Starts a new DeltaWalker Classic instance for this comparison instead of passing it to an instance that is already running. The command then returns only when you quit that instance, which is what SCMs that wait for their diff or merge tool expect. The integration scripts that come with DeltaWalker Classic use it.
-nomru: DeltaWalker Classic does not reopen the file and folder comparisons that were open when it last quit, regardless of the Launch most recent comparison(s) on startup setting on the General page of the Settings window. Use it when one of those comparisons keeps DeltaWalker Classic from starting up; once it is running, you can delete that comparison.
-title1= -title2= -title0=: Labels that DeltaWalker Classic shows, read-only, in the path fields above the panes in place of the paths, to help you identify the files. -title0 refers to the Reference: the first resource in a two-way comparison and the middle one in a three-way comparison. -title1 and -title2 refer to the first and second modified resources.
-script=: The path of a script that DeltaWalker Classic opens and runs when it starts. Scripting is part of the Pro and Oro editions; see Scripting.
-vm path: The Java runtime to run DeltaWalker Classic with. DeltaWalker Classic comes with its own Java runtime and uses it by default; use this option only to run it with a different one.
-nosplash: Accepted for compatibility with existing scripts. DeltaWalker Classic starts without a splash screen on every platform.
-vmargs [Java VM arguments]: Customizes the Java VM that runs DeltaWalker Classic. If you specify it, it must come last on the command line. The arguments you can pass depend on the VM.