Where Does SemanticMerge Store Settings?
SemanticMerge reads semanticmergetool.conf from its user directory, defaulting to Local AppData on Windows.
Last updated
SemanticMerge keeps its tool configuration in semanticmergetool.conf, read from the SemanticMerge user directory or from beside the binaries. That file wires external text tools like KDiff3 into the semantic flow for method bodies and properties.
Git integration itself lives in your .gitconfig as difftool and mergetool entries pointing at the install, commonly under Local AppData. Keep the two apart: .gitconfig decides when SemanticMerge runs, the conf file decides how it behaves.
Where SemanticMerge stores this, by platform
%LOCALAPPDATA%\semanticmerge\semanticmergetool.conf
Tool wiring such as -edt and -emt external tool params. Falls back to the install folder copy when absent. Git side lives in ~/.gitconfig difftool and mergetool sections referencing semanticmergetool.exe.
Frequently asked questions
How do I use SemanticMerge with Git?
Point git difftool and mergetool at semanticmergetool.exe in your .gitconfig with the documented command lines, and disable prompts. Test with git difftool on a branched file before trusting it mid merge.
Where do I configure an external text tool in SemanticMerge?
In semanticmergetool.conf in the user directory above, using -edt for diff and -emt for merge tool commands. The bundled Xdiff/Xmerge handles method level work while your tool takes the text bodies.
Notice an outdated path? Let us know.