Request: Settings import/export

Support for our DiffMerge utility.

Moderator: SourceGear


Posts: 5
Joined: Thu Jan 28, 2010 5:44 pm
PostPosted: Thu Feb 25, 2010 11:12 am
It would be really great to be able to import and export my DiffMerge settings to share with co-workers.

Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Thu Feb 25, 2010 11:24 am
I will enter a feature request. Thank you for the suggestion.

F: 15270
Beth Kieler
SourceGear Technical Support

Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Thu Feb 25, 2010 1:33 pm
In the meantime, you could try exporting and importing the registry settings for the tool. So that I can tell you where to look can you tell me if you are using just the DiffMerge that came with Vault or Fortress or using the separate DiffMerge tool?
Beth Kieler
SourceGear Technical Support

Posts: 5
Joined: Thu Jan 28, 2010 5:44 pm
PostPosted: Fri Feb 26, 2010 9:46 am
The separate DiffMerge tool.

Posts: 534
Joined: Tue Jun 05, 2007 11:37 am
Location: SourceGear
PostPosted: Mon Mar 01, 2010 9:20 am
Sorry, but import/export of preference settings didn't make it into the last release.
If you're brave, you might try moving copying the various config files/registry settings.

On MAC, we have a single config file: "~/Library/Preferences/SourceGear DiffMerge Preferences".
On Linux, we have a single config file: "~/.SourceGear DiffMerge".

Both of these are text files (and very similar to a .INI file).

On Windows, all of the settings are stored in
HKEY_CURRENT_USER\Software\SourceGear\SourceGear DiffMerge
There are lots of sub-keys and name/value pairs within this. You
should be able to export the top-level key to a .REG file and then
let someone else import it. (Or if you are only interested in a particular
set of vaules (say ruleset settings), just get the stuff in
HKEY_CURRENT_USER\Software\SourceGear\SourceGear DiffMerge\File\Ruleset)


In all cases you should exit DiffMerge before copying the settings (we
write out some of them as we shutdown). Likewise, the importer should
close DiffMerge before attempting to import them.

If the recipient has any problems using DiffMerge after "importing", just
have them delete the new stuff and relaunch. DiffMerge will create a
new file with the builtin defaults the next time it starts up.

Hope this helps,
jeff

Return to Support (DiffMerge)

Who is online

Users browsing this forum: No registered users and 2 guests

cron