Press Ctrl+O or select the “Select Files/Directories…” item in the File popup menu to open the selection dialog. Enter the left-side and right-side path — a file, a directory or an archive, in any combination — either directly, via the drop-down history of previous selections, or with the Dir… / File… browse buttons. After the selection, both sides are analyzed, compared and displayed. The dialog can be made larger by dragging its edge: the width goes to the path and Exclude fields, the height to the list of saved configurations, and the size is remembered for the next time.
The dialog is not the only way in. You can also drop files or folders from the Windows Explorer onto the Diffoniq window: drop two at once to compare them, or drop a single one onto the left or right pane to replace just that side and keep the other as it is. Dropping onto an empty window is fine too — that side is shown on its own until you supply the second. Exclude patterns that are in effect stay in effect: a drop changes what is compared, not how. Starting Diffoniq with two paths on the command line does the same without the dialog.
If one of the paths contains wildcard characters, a directory listing
filtered by that pattern is displayed instead. The filter applies to
files only: subdirectories are always listed and scanned, so a mask
like C:\src\*.cpp still compares the whole tree. Several masks
can be combined with semicolons (e.g. *.cpp;*.hpp); matching is
case-insensitive, ? stands for a single character, and
*.* means every file — with or without an extension.
Each side has an Exclude field: one or more wildcard
patterns, separated by semicolons (e.g. *.bak;tmp), for files and
subdirectories that should not appear in the directory comparison —
typical candidates are backup files, build output or version-control
folders. An excluded directory disappears together with its whole subtree.
The same patterns and rules apply as for the path masks above, and they work
inside archives as well. An empty field shows
the example *.bak;tmp in grey.
For longer filter lists, the … button next to each Exclude field opens an editor that shows the same list with one pattern per line — add, change or delete lines there instead of scrolling through a semicolon-separated string. The window can be resized (it keeps its size for the rest of the session), and OK writes the patterns back to the Exclude field; blank lines and surrounding spaces are ignored.
Whoever compares two working trees — a repository against its backup,
two clones — usually wants to see neither node_modules nor
build, .vs, bin or obj.
The list of such folders already exists: in the .gitignore files
of the tree. The checkbox Hide what the .gitignore files of both
folders ignore, below the two sides, applies those rules as a
further exclude filter, on top of the Exclude fields. It is off unless you
turn it on, and it is saved with each configuration like the Exclude
fields.
The checkbox is greyed while the filter cannot matter, and its label says
why: when a side is a file or an archive (folders only), or when no
.gitignore and no .git entry is in sight (none
in sight here) — at the folder itself, in a folder above it, or up
to three levels below it. That look below is shallow on purpose, so a large
folder keeps the checkbox available: its repositories may lie deeper.
What is read: every .gitignore in both trees, each in force
from its own folder downwards, as in git; the .gitignore files
above the compared folder up to the repository root (the nearest
folder holding a .git entry), so comparing repo\src
hides what git would hide there; and that repository’s
.git\info\exclude. The user-wide
core.excludesFile of git is not read — it depends
on the computer, and two people comparing the same folders should see the
same. The .git folder itself is always hidden while the filter is
on. The full rule syntax of git is understood: comments, negation with
!, patterns anchored with a leading or inner /,
folder-only patterns with a trailing /, *,
?, ** and character classes; upper and lower case
are not distinguished, as git on Windows does not.
Each side follows its own .gitignore files. Where a side has
no file in a folder, the other side’s file for that folder applies there
too, so a backup that lost its dot files still hides the same
node_modules, and nothing appears as “only right” for
that reason alone. Where both sides have a file and the rules differ, the
verdicts differ as well: a docs folder ignored on the left but
kept on the right is listed as “only right”, because on the right
it is real content. A hidden folder is never read at all, which makes the
comparison of a tree with a large node_modules noticeably
quicker. What the rules hid is counted in the status
bar (“n hidden by .gitignore, m on one side only”), in a
report and in the sync log, so
a filtered comparison is never mistaken for a complete one. A
synchronization never touches an entry that the rules
of either side hide — it neither copies nor deletes it, even
when the other side lists it. The filter works on folders in the
file system; inside archives only the Exclude
fields apply. On the command line the switch is
/gitignore.
The Saved list stores complete selections — both paths, both exclude filters and the .gitignore switch — each under a name of your choice. Type a name in the Name field (or leave it empty for an automatic one) and press Save; a short confirmation appears below the list.
Click a configuration to load its fields (so you can review or adjust the parameters), and double-click it to load and start the comparison in one step. Delete removes the configuration named in the Name field (or the one selected in the list).
While you edit the fields, the list tracks what you have: when the fields match a saved configuration it is highlighted automatically; once you change a parameter of a loaded configuration, the status line shows it as (modified). The list keeps the most recently used configuration on top: confirming a selection with OK moves its entry to the front. Saving under an existing name replaces that entry.
On the next start, Diffoniq restores the selections from the end of the previous session. Command line arguments take precedence over the restored settings.