In other words, if you:

- Select a big file
- Click the "Force Compare" button
- Use the "Go to previous change" or "Go to next change" buttons until you reach the start or end of the file

it would be nice if SmartGit wouldn't select the previous or the next file. Because then you have to wait again for the compare to be computed for the big file.

Instead of only showing "File is too large to display.", could you please add the output of git diff for that file (perhaps just the first 10,000 lines/characters)? This at least gives *some* information.

There is also a delay before the "File is too large to display." It would be great if that delay could be removed, perhaps by estimating whether the file will be too large based on just the file size.

I work in a repository where there are several large files that must be updated in almost every commit, but the changes are tiny; just being able to see the change quickly would be ideal. 

This started happening after the latest update: 19.1.1 #14179

After I open the Conflicts Solver window:

I also open the Base Changes window:

And when I think I am done, I close the Conflicts Solver Window.

But now, Smartgit is automatically closing the Base Changes window when I close the Conflicts Solver window. Very bad! How can I post review changes now?

I would also like to ask to:

1. Not close the Base Changes window, just because I closed the Conflicts Solver window.

2. Allow me to reopen the Base Changes and or the Conflicts Solver window, after I marked the conflict a solved, so I can refix something I bad merged/fixed on the last time I had those windows opened. Now, I can only do that by aborting the whole merge process and starting everything from scratch.

Most times the conflicts I solve are so hard to deal with, I have to open the text editor to properly deal with them (like rewrite code).

But when I go back to the Smartgit `Conflict Solver` window, the changes in the file system are not reloaded. 

It would be very welcome if Smartgit asked me whether I would like to reload the changes on the file system
.

Why oh why did you make the Reset command now become a hard reset? I never do a hard reset always a mixed one, and because of your changes, I have now lost a whole day's worth of work. The default reset should most definitely be the safer option of mixed so that you still have your changes

A (very small) improvement for the tag-diffs:It would be great to do the following:

• Select 2 (or more) Tags
• Reveal (from context menu)
• expected:
  • Selected 2 (or more) commits are revealed
  • diffs are shown in case 2 commit are revealed
    

This would be the perfect UI for me to diff tags, especially if commits are far away from each other.

Currently, one can filter the Files view by, e.g., "*.txt, *.php". What about searching for file name parts, e.g. "file man" to find SgFileManager.java?

When viewing a commit, it would be nice to be able to either:

a) right click on the file in the Files tab and select "View Before" or "View Before", or

b) select "View" from the appropriate Changes window down the bottom of the screen

and it would save the file to the %TEMP% folder and open my editor for it.

At the moment my options are either copy the text from the Changes window and paste to my editor (but since the new unsaved file doesn't have an extension, it doesn't get syntax highlighting), or save the file somewhere and then open it in my editor.

I just want to view the file - not revert it, and I don't care where it gets saved.

Currenly the number of current different line is marked (yellow) only on one (focused) side of Changes window. If user is looking into the code in other side, (s)he will hardly see this mark.

It would be handsome if current line's number was somehow marked on the non-focused side too, f.e. with gray.