Thanks a lot, this works!

I have no SSD, but 2 HDD (1Tb + 2Tb). I don't know if the default search runs on the whole HDDs, but this default search takes at least 2min20s the first time I open Smartgit and use "Search for Repositories". Apparently after this first default search, I can leave and relaunch Smartgit and then the default "Search for Repositories" takes only a few seconds, until I reboot the workstation.

Well, it's not a big deal, but I wanted to let you know about it.

This is mine for p4merge. Apparently your config is fine except that the argument order is not the same for p4merge. 

Actually the bcompare doc sounds weird to me:

3 files = BCompare.exe C:\Left.ext C:\Right.ext C:\Center.ext

4 files = BCompare.exe C:\Left.ext C:\Right.ext C:\Center.ext C:\Output.ext

So in "3 files" context I assume that Center.ext=${mergedFile}

In your Smartgit config you assumed Output.ext=${mergedFile} which seems fair as it's called "Ouput.ext" but may be you could try this argument order:

 ${leftFile} ${rightFile} ${mergedFile} ${baseFile}

As stated in one of my previous comment I did manage to make this works with p4merge using ${leftFile} ${rightFile} ${baseFile} ${mergedFile}

I think it should work with bcompare too. Are you sure that you use the latest smartgit version? because baseFile has been introduced at some point and wasn't existing in the first smartgit versions 

As already answered by Thomas Singer, you can focus the Git Commits view and directly type (or paste with CTRL+V) what you're looking for (SHA1, description, author) and you'll see a "Search For:" input appear at the top left corner. Then you can hit F3 or SHIFT+F3 to go to the next or previous match

Hello Don,

I agree with you buit if SmartGit team prefers to have the base and the working tree in two distinct windows, then I say "fair enough" :-). I guess it's not such a big deal.

I'm actually using p4merge in Smartgit at present. But there's a drawback that I've not searched to fix yet: when I click on "Conflict Solver" in Smartgit, it does open p4merge but SmartGit instantly asks me if I want to stage the file instead of waiting for me to close p4merge. It's probably because p4merge command release back the shell prompt immediatly actually.

It looks good indeed. If I may suggest something minor: I wish I could see the 4 views at the same time: left (ours), base, and right (theirs) on the first line of the window and the working tree below.

n.b: sorry if it's not the place for that but it took me some time to get the JRE 1.8 running on my Debian 7 (wheezy) as the GLIBC 2.14 required by .smartgit/8.1/swt.tmp/libswt-pi-gtk-4712.so. I was thinking to post an howto about that. Should I post that to the smartgit google groups, mailing list or somewhere else ?

Thanks you very much! I think you forgot to post the link but I guess this is the one https://www.syntevo.com/doc/display/SG/Blame

So this is in the Blame window right ? I've never used it so far but it seems it has exactly what I'm looking for. Perfect !

Thanks for the answer. Sorry but I don't understand what you mean by "chaging the View Commit". So forth I don't see where is "the History of current line". I guess we're talking about the SmartGit Log window, don't we ? I'm on SmartGit 8.0.3 by the way

By the way, I realize that's what DeepGit does, isn't it ? http://www.syntevo.com/deepgit/