Joel also provided a solution here in case you run Mercurial under Cygwin.Įxplanation of WinMerge command line args here. ![]() This same approach can be used to add nearly any visual diff tool, but be aware that your diff tool must be able to support directory diffs if it is to be used by TortoiseHg, unless you are using release 0.8 or later. or Right-click your project suite in the Project Explorer and then click Source Control > Visual Diff. Select File > Source Control > Visual Diff from the TestComplete main menu. You can use this tool to compare any two similar files, but the most popular use for it will be to. On the TortoiseHg tab, you should see winmerge available in the drop-down list for Visual Diff Command. If you use TortoiseHg to work with Mercurial from TestComplete, you can use your visual diff tool specified by Mercurial settings to view current changes. TortoiseHg includes a visual diff tool called KDiff3. ![]() VCS IntegrationTortoiseSVN, TortoiseHg, TortoiseGit, Team Foundation. Share Improve this answer Follow edited at 6:57 answered at 13:51 Geoff Appleford 18. Code Compare is shipped both as a standalone file diff tool and a Visual Studio. TortoiseHg to detect visual diff tools in release 0.10, much as it > detects merge tools today, and for THG to come preconfigured to use > those visual diff tools in the best way possible. Add these lines to your personal Mercurial.ini fileĬmd.winmerge = C:\Program Files\WinMerge\WinMergeU.exe Visual Diff Tool in TortoiseHg Global Settings had to be set to ' beyondcompare3 ' instead of ' bcomp '.
0 Comments
Leave a Reply. |