Hello everybody, my name is Damion, and I'm glad to join your conmunity, Then it will always do the recursive directory comparisons by default. So the tip is to go to your SendTo folder, right click the WinMerge shortcut icon, open its 'properties', and change the target to include ' /r ' at the end. That way, they can select two files, or two directories, and then Right Click and say SendTo - WinMerge.īUT that will default to NOT being a recursive directory comparison. Most people drop a shortcut to WinMerge into their 'SendTo' folder. Oh, and you know that little part of you that dies when you see the WinMerge screenshots? It's just your gall bladder, and I don't think those are really even necessary. Richard Hale Shaw will be with me, bring whoever you'd like.
Why don't you give the 30-day trial a shot and then come back and tell us how much it sucks?Īll right, that's it.
Designed by programmers, for programmers. And a little part of me dies inside when I look at the WinMerge screenshots. Programmer tools- not so much known for their helpful UI. This is not an inconsequential issue or a trivial thing for a program to get right. Such programs are rare, and when you find one it's like making a new friend.īeyond Compare is one of those rare gems that doesn't just blow the competition away in terms of features, but manages to pack all of these features into a user interface that is a joy to use. Sometimes you come across a program that seems to be one step ahead of you, anticipating your need and surprising you by implementing features you cross your fingers and wish for when you go looking in the options dialog. It's mostly usability and UI related, which I COMPLETELY agree with:
I usually only argue with you because it's the best way to got get me some schoolin'. You can set that via Tools > Options > Local Files > Check "Detect Modified Files using CRCs instead of modification times"Īnd I still respect your opinion. Otherwise I end up with tons of files that say they're changed, but aren't. Oh, and one other Vault tip - use CRC's to determine changed files when working in CVS mode. More info on the Vault Diff/Merge Options here. More info on the WinMerge commandline args here. Merge Arguments: /dl "%WORKING_LABEL%" /dr "%OTHER_LABEL%" "%WORKING_PATH%" "%OTHER_PATH%" "%DEST_PATH%".Diff Arguments: /dl "%LEFT_LABEL%" /dr "%RIGHT_LABEL%" "%LEFT_PATH%" "%RIGHT_PATH%".Default is C:\Program Files\WinMerge\WinMerge.exe\
Diff Program and Merge Program fields: Path to your WinMerge.exe (or WinMergeU.exe if you need Unicode support).In Vault: Tools > Options > Diff/Merge tab.I know it sounds kind of crazy to use experimental builds of a diff / merge tool, but these guys have been putting out very high quality releases for years and their betas are better than most finished products, so if you're feeling lucky go with the latest experimental build. I've been a fan of WinMerge for a while, so when I started using SourceGear Vault this post was pretty much inevitable. Diff / Merge against source control is something I do very frequently, so I think it's worth the few minutes to use the best possible tool.
I previously blogged about how to use WinMerge as the diff tool in StarTeam.