[feature-request] use +0 when calling vim to collect commit message

[TLINDEN]

I'm not sure, if gitu calls vi[m] or $EDITOR itself of if it just calls git commit. If it calls it itself, then it would be good to add the +0 argument.

Currently it looks like this: I change a file, commit it and enter a commit message. I end up in line 4. Next time I want to enter another commit message, vim starts on line 4 again, so this time inside the comment section. I have to move the cursor to the top to enter the message.

[altsem]

@TLINDEN Gitu just runs git commit, so git would be responsible for opening the editor.

The case is not the same when you open a file/diff with "enter".

I take you get a different result when running git commit from the terminal?
Seems odd 🤔