Bash is by far the most straightforward interface. For visualization of branches, source tree does a fine job. Bash can be very fast though, especially if you use aliases to shortcut common commands. Shells are interfaces for users in case anyone is confused by my response. GUIs are a specialization of UIs also 😏

Case

FirstControl.Enabled = SecondControl.Enabled = enabled;

These are reasons I tend to go with solutions that give no luxuries like drives to have data stored on to loose. I have been using Heroku, as one example, for several years. Every time I make a change to the source code and push that change to my application, whatever server my app is living on gets wiped out and the source is fresh from git. In fact every time I restart the app or scale up another server, this same thing happens. Everything that needs to be persisted is stored in s3 or in a database. I like to think of it as another separation of concerns. Nothing but code, which is redundant in git, is stored on the server. Environment variables get dynamically loaded each time the server starts for any configuration settings.

It bothers me a great deal and for very specific reasons. When working in a team, it is not good enough to clean up someone else's code by running an auto format tool. Depending on the tabs vs spaces issue this can potentially be a far from trivial task. Additionally, if you do just clean up every file in a project before you commit your changes, you may be horribly polluting the commit history and your diff will give no one on your team any clue as to what you actually implemented. It's a dangerous game that will compound over time. Best is to review code as a group and set up all of your editors to be consistent. Then define a standard art form that you all agree on. Anything less than that and you're asking for a world of hurt.

Rubykoans is a great place to start. It's test first learning so you'll fall right in line with the rest of the community's expectations.