Your comments

Instead of "switching back" can SG devs improve the new one with this feature the prior had? I would like that more because I appreciate the improved diffs; I also miss the "stage lines" that worked better of the prior implementation.

Oh duh, of course.  Thank you.  Wish I had thought of trying that!


My original thought was to remove items that didn't match for clarity, but that's a low priority/luxury item.

This is not a feature I have needed a lot, but could use this feature right now. :-)


I just encountered this problem again yesterday - I forgot to look at the Output view for errors, so kept trying things incorrectly.  I like having the Output view open for regular reviewing/watching progress, therefore SG won't display a popup on errors.  Is there any feature option can add to strongly/interruptively notify user when problems detected?

That works for me.

The key thing is auto-formatting to the correct length while typing, whether it uses hard newlines or not in the control, and then submits with hard newlines as formatted.


Maybe OpenOffice|LibreOffice has something, but I would look at how gitk and git gui do it.

Using Windows.


Yes, risk exists with killing the running process.  I was thinking of letting the current process finish but not starting another one - cancel running the rest of them.  Is this possible?


Additionally, is it possible to not disable a few options, such as Log and the "Open" operations, during the background fetch operation?