I've understood exactly this. Currently, we just fill our compare with the file contents and the view compares them itself. Using a diff output would require to first have the compare result and then fill the view. This would require major refactoring effort - for the benefit of a harder to read result.

The "diff" view is not the preferred view but just the simplest implementation because it is the result of an invoked command and hence used by plain Git command wrappers.

The "Dark theme" option in the SmartGit preferences, page "Built-in Text Editors", only has influence to the built-in text editors. I'm currently playing with a full-app-theme but the API is extremely limited and hence the results very bad (see the above bugs.eclipse.org link).

What exactly did you do on OS X and what does not work?

All who are interested, please vote for https://bugs.eclipse.org/bugs/show_bug.cgi?id=500720.

I posted this request because of feedback from large companies. According to this there are a lot of average users who don't really understand how Git works and don't want to learn it - they just want to commit their changes. It would be in the team's interest to hide potentially dangerous commands for those users, so they can't damage anything by mistake.

SmartGit already saves its settings as files (in its settings directory - see the about dialog for its location). You may create a repository for this directory on your own.

Aurelijus, please try the Vivacious-unity-zblackout-aqua dark theme.

This is a context menu that contains menu items that can operate on the selected files. Stash does not operate on selected files, but always on the whole repository. Hence I voted against this request.

Mark your repository as favorite. This will automatically fetch the latest changes.