Path = c:/program files/Beyond Compare 4/bcomp.exe
Here is the entry which foxes git to launch beyond compare 4 instead. gitconfig file would have been sufficient to get going: īut if you want to change the default associated tool then you end up mentioning the path attribute separately so that git gets to know the path from where you new tool's exe has to be launched. if I had installed beyond compare version 3 on my box then having below configuration in my. Known key then you would not need to run the second command as their installįor e.g. If you map well known version of tools to appropriate already existing/well. If I wanted I could have mapped it to any of the pre-defined keys in the above list also e.g. I didn't have beyond compare version 3 on my computer so I didn't care. I can map beyond compare 4 tool to already existing key bc3 which corresponds to beyond compare 3 version. So you can follow any of the below approaches: beyond compare is a well-known tool to git but its version 4 release is not mapped to any of the existing keys by default. Like in my case, I had installed beyond compare 4. A new version of an existing well known tool has got released which is not mapped to any pre-defined keys in git?.What if you have to setup a comparison tool which is
BEYOND COMAPRE VS P4MERGE FREE
If you want to setup a new tool altogether(or a newly released version of well-known tool) which doesn't map to any of the keys listed above then you are free to map it to any of keys listed above or to a new custom key of your own. You can use any of the above keys or define a custom key of your own. If you want to see all pre-defined keys just run git difftool -tool-help command on git bash. This is a well known key to git corresponding to a particular version of well known comparison tools available in market ( bc3 corresponds to 3rd version of Beyond Compare tool). Path = c:/program files/Beyond Compare 3/bcomp.exe You will know it in a short while): git config -global "c:/program files/beyond compare 3/bcomp.exe"Ībove command creates below entry in. Then you run below command ( Running this command is redundant in this particular case and is required in some specialized cases only. gitconfig found in %userprofile% directory: The above command creates below entry in. The first command that we run is as below: git config -global diff.tool bc3 I'll just elaborate more on accepted answer.
0 kommentar(er)
