The Commit window is a dialog and IMO it does not make sense to duplicate functionality here. Instead, you may build your commit message step-by-step using Window|Commit Message.

Open From Working Tree will do the same as Query|Open from the main window, especially configured Tools (from the Preferences) will be applied. In your case, there seems to be a Tool configuration which points to the invalid path "C:\Program Files (x86)SmartGitHg\git\GitT\Bash.vbs".

As a workaround, you can just open Window|Show Working Tree Window .

I think there are better solutions. Maybe this can be merged with: https://smartgit.userecho.com/topics/835 ?

We are quite reluctant to add columns to the Log Files view which only have a meaning for working tree files, but not for commit files.

Maybe this problem is less relevant in version 18.2 Preview where you have all working tree operations available in the Log windows and there you have separate Index and Working Tree nodes?

> Would it make sense to do the same for Log (Ctrl-L)?

What exactly do you mean here?

Did you already give 18.2 Preview a try?

SmartGit 18.2 preview build (13104+) contains a new low-level property (Preferences, Low-level properties):

log.graph.preserveConnectorsUntilFork

Which in combination with:

log.graph.forkRightMost

yields graphs very similar to other Git clients. This should at least partially obsolete this request. If you want to explicitly specify the display order of graph branches, vote for https://smartgit.userecho.com/topics/833.

I guess this is something which could be displayed in the Details view, instead of displaying in a separate window. Though, I'm not sure on computational overhead compared to the Git tree diff which we do currently. Hence, maybe it should be optional.