It is also possible to open the log before starting the interactive rebase.

This is no general interactive rebase problem but one with your particular repository - most likely you have committed line separator changes unintentionally. Again, userecho is NO support forum.

What do you mean with "it doesn't work the same way as the Journal"?

What do you mean? How is the Index Editor related to the Interactive Rebase? Please note, that this is NO support forum here.

A first implementation of the (optional) compact presentation looks like this:

It means:

• no syntax coloring
• no ability to apply changes in the repository's Changes view

SmartGit should not be a bad editor and support/write mixed line separators. If mixed line separators were detected, it will reject editing.

The devil is in the detail, e.g.: what line separator to enter when the user presses <enter>, especially if the file is empty. How to handle text copy-pasted from some other source?

You may put this command sequence into a shell script and add an SmartGit tool to this shell script.

What exactly do you mean then with "execution of a command itself"? What command you like to invoke?

No, it is not possible to detect reliable in what branch the commit was created. The merge comments might be a clue for the one who reads the log. The primary parent for branches also might help. But I have seen more complex repositories (using excessive merging for feature branches) where it was impossible to determine the branch, especially because there was none any more.