So you are always free to map any tool to any of pre-existing keys or to a new custom key of your own. there is no key for Beyond Compare v4 in above list. Similarly, this problem can occur for a newly released version of an existing tool also e.g. Eventually Git will show it in a future release but not immediately. For obvious reasons the current version of Git installed on your machine will not show any key corresponding to this new tool. let's say we're setting-up a brand new comparison tool which has just been released to market. for Beyond Compare v1 we'll use the key bc, for Beyond Compare v3 we'll use the key bc3.īut in some cases, we might have to define a brand new key of our own e.g.
While setting up a comparison tool for Git, we can use any of the above pre-existing keys based on the tool and its version you're using e.g. When we run above command then it returns below list: vimdiff If you want to see complete list of the keys maintained by Git then run below comand on Git Bash command-line: git difftool -tool-help in this case bc3 corresponds to 3rd version of Beyond Compare tool.
This is a well-known key to Git which maps to a particular version of a specific comparison tool available in market e.g. The most important thing to know here is the key bc3. We will know its reason in a short while from now. It is required in some specialized cases only. This is all you required while setting up an already published version of any well-known comparison tool which is already known to Git like in this case 3rd version of Beyond Compare is known to Git.Īdditionally, you might be required to run the below command also: git config -global "c:/program files/beyond compare 3/bcomp.exe" %userprofile% is an environment variable which you can type on Run prompt and hit Enter to open the directory location where. gitconfig file 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 All the details that I've shared are equally useful for any diff tool in general, so I am sharing it here. Reproducing my answer from this question which was more specific to setting Beyond Compare as diff tool for Git.
0 kommentar(er)
