SourceGear Support

Looks like the link to previous releases got removed from the downloads page.
Here are links for the 3.3.2 release:

http://download-us.sourcegear.com/DiffM ... 1_i386.deb
http://download-us.sourcegear.com/DiffM ... _amd64.deb

jeff

you're right. i overlooked it in the backlog.
i've scheduled it for 4.1 so i won't miss it again.

thanks
jeff

Try the Command+Option+xxxxx keys.

I'm not sure why, but it looks like when I
switched from the Carbon to Cocoa libraries
the keybindings got switched.

I've logged this.

thanks
jeff

Try setting "Exact Match or Ruleset" and turn on "Enable Default Ruleset" on the "Equivalence Mode" page of the Options dialog. You should then see the "nearly equal" files as marked "equivalent" in the folder window. Let us know if that doesn't take...

Since this has been one of our most frequent questions/requests
I thought I replay here and say that this has been addressed in 4.0.0
which we just released.

jeff

SourceGear DiffMerge 4.0.0 is Now Available. See http://www.sourcegear.com/diffmerge/ for more information. The release notes can be found here: http://www.sourcegear.com/diffmerge/webhelp/sec__release__4_0_0.html Packages for Windows, OS X, Ubuntu, Mint, and Fedora can be found here: http://www.sou...

Let me attempt to address each of your questions/requests in turn. [1] "differences only into a new file": There is a "--diff=file" option that will compare the 2 files and write standard diffs to a new file. You can add "-u" to get unified format diffs. diffmerge --dif...

That's odd. We haven't seen that one before. If its what I suspect, this should take care of it: Exit DiffMerge. Edit the file "~/Library/Preferences/SourceGear DiffMerge Preferences". Add the following to the bottom of the file: [Hack/Mac] HackForceActivateOnLaunch=0 Save that and then tr...

Sorry, but DiffMerge doesn't currently have a way to ignore things like that.
We've had several requests for a way to ignore things like line numbers
either by field or by column range, so you're not alone in asking for it.

I'll log another vote for it.

thanks
jeff

I think you're having a different issue than "deeprus" is/was having. I think his files were UTF-8 without BOM's. You mentioned CP1251. Are your files CP1251 rather than UTF-8? If you have CP-based files, look at the Options dialog and go to the corresponding Ruleset and select the "C...

Right.

That feature didn't make it into the core DiffMerge program when
I made the last cut. So neither the stand-alone release nor the
releases bundled with Vault or Veracity will have it.

On the View Menu there is are commands to change it from 2 to 4 to 8 spaces.
Unfortunately, it is a global setting. I wanted to make it per-ruleset, but that
didn't make it in.

I'll log a request for this.

Thanks! we do support taking folder arguments on the command line and will open a gui window with the 2 folders. what we don't support is taking folders on the command line and having it print the list of changed files to the console/stdout. i haven't looked at git's config settings recently, but it...

... for example "\xd0\x90\xd0\xb4\xd1\x80\xd0\xb5\xd1\x81") ... The \xd0... characters are the raw UTF-8 multi-byte sequences. That dialog shows the first few raw bytes of the file and is asking for help to figure out what the encoding is, so it doesn't yet know that \xd0\x90 is a Cyrilli...

I'm not sure why it isn't working for you. Could you send me a zip or tar file with those 2 files ? Either post it here or email it to me at jeffh at sourcegear.com. It would help if you also included the contents of the Support Dialog (available from the About Dialog). That will show me all of the ...