This might help a lot for those who have to use macOS, but primarily on Linux and/or Windows.

Have different syntax coloring themes that easily can be switched. One should be the custom one where colors can be changed by the user.

I am using chezmoi to synchronize files between my computers (dotfile manager) https://www.chezmoi.io/.

For example, suppose I'm working on ~/dev/my_project and I have a dotenv file that I want to  synchronize (~/dev/project1/.env) to my new laptop

Then on my new laptop, after I recover my dotfiles from my previous computer (which creates the project1 folder with my dotenv file), when I try to clone git://xxx/my_project.git to ~/dev/my_project, it detects the folder already exists, and clones into a new subdirectory ~/dev/my_project/my_project.git/ instead of just cloning inside the existing folder (and optionally asking to erase existing files but the .env file is gitignored in my case).

It then becomes nerve-breaking to fix things up.

Can we add an option to clone into an existing directory + even if it has some files ?

I have the "log.useCommitMessage.prefix" low-level property configured to "fixup! ".

Currently to use this to make a fixup commit from the Standard view I currently have to hit the History button to switch to the commit graph, select the commit I want to fixup, and then hit the keyboard shortcut for "Use Message for Commit".

It would be great if this was more streamlined and could be done without switching away from my local files. Ideally the message prefix could be inserted when clicking on a commit message in the mini-log displayed below the commit message field.

It would be nice if adding files that are large would automatically track them with Git LFS. 

A filesize value as threshold would help (i.e. on add if file larger than 1MB -> git lfs track file)

If my repo is marked as favorite, I want to know if there are changes to the main/master branch while I currently have a feature branch checked out. It currently only seems to notify me if the main/master branch is checked out.

If the Branches pane is used to show/hide branches, then this may change the height of the displayed log tree. This has the effect of shifting the Graph window contents up or down.

If there is a commit selected and visible in the Graph window, then as possible the selected commit should be kept in-place as other branches are shown/hidden. Otherwise, the commit may move or even jump off the screen, which is confusing.

This won't always be possible (e.g. hiding a branch which is the only branch at the top or bottom of the visible area), but when it is it would be nice.

SmartGit shows an "Abort" button in a "The working tree is in merging-state" bar when you're in the middle of a merge. But, you have to know that to "merge" you click on the standard "Commit" button.

Proposal: add a "Merge" button to the left of the "Abort" button.

After running some git operations, I can see the git output by clicking on the green bottom status bar:

But showing only the last output is not enough to remember complex operations done successively. Access to its history other than just the last command is similar to running all git commands in a terminal, and it is pretty helpful to audit which git operation I had done and how they went. Just showing the last command is not enough to understand complex changes in the process.

I am not asking to remember the output after I close the Smartgint Standard Window, but to keep them while the window is open (as you already do with the Working tree and Log window). There is no see to use fancy formatting as done with the Working tree or Log Window. Just plain the text output of the command output is needed, and more than enough (and, of course, knowing the exit status of the git command is also essential; it just does not need to be fancy).

You could limit the maximum number of lines with a low-level property if you did not do this already. Because you are now saving only one command, it does not mean its output will be small.

On the log or working tree windows, I can have the git console output to see past git operations history.

This is useful for remembering hashes and whatever I had done with the project. Its history is similar to running all git commands in a terminal, and it is pretty helpful to know what Smartgit is doing behind the scenes and audit its git commands.