I’ve been using Node.js quite a bit lately and decided it was time to start using Git for my projects.
I’m used to using Mercurial (Hg) for DVCS, but have only used it on Windows and a little on Linux via command line.
I was looking for a similar experience that Windows gave me for Hg (file explorer integration with tortoisehg), but for Linux. I had created a repository using tortoisehg. When I attempted to add files to the repository using tortoisehg or straight from the command line, I was getting a few errors. tortoisehg, nautilus integration is broken on my distro at the time of writing this too. So this encouraged me to invest a little more time in Git. I had done a bit of reading and listened to a few good podcasts on Git, so I felt it was a good time.
think like a git is also good for a read.
As I was creating repositories, dealing with remote repositories, cloning, setting up all the config files, adding, committing, pulling, pushing, viewing status and diffing. What I quickly came to realise, was that the Git commands were very extensive, made more sense to me than Hg, and there is a lot of good documentation around. In saying that, it’s been a while since I used hg from the command line and most of my work has been through the GUI tools.
One area I was struggling with was the diffing of files and directories on the command line. There are a couple of good ways to make this experience a lot more pleasurable.
I like using meld on Linux for my file and directory comparisons, so already had that installed.
Create a bash file in the /bin directory.
I called it git-meld, and it looks like the following:
#!/bin/bash meld $2 $5
Turn the executable bit on, so it can be executed.
chmod git-meld +x
Now modify your ~/.gitconfig file
git config --global diff.external git-meld
To make sure your’ve added git-meld as the script that’ll run meld with the correct parameters:
and you should see at least the following:
[diff] external = git-meld
Now that should be all you need to get git to pop meld on diff.
git diff [options] <commit> <commit> [<path_to_file_to_compare>]
If you have a stack of files (rather than just one, as shown in my above example) that were changed between these commits, diff will pop each file open in meld. One at a time until you’ve finished with each one
git also comes with difftool. I found this really nice to use. There is no setting up for it. All you do is replace the diff command with difftool. Optionally you can specify the GUI diff tool you want to use, simply by appending -t [your_GUI_diff_tool] like this if you like using meld.
git difftool -t meld <commit> <commit> [<path_to_file_to_compare>]
If you do this without specifying the file you want to compare, you are prompted if you want to view each file, rather than how diff works by just opening every one.
If you choose to leave the -t option out, difftool will give you the option of all the possible tools able to perform the diff (some of which may need installation).
So using difftool is a better diff IMHO. This is how git difftool behaves whether or not you set up ~/.gitconfig file with your prefered diff tool.