When a conflict is resolved, it still uses a red color in the scroll bar, meaning there's no easy way to check which ones are solved and which aren't.

Right now, it's hard to check which block was selected as part of a review: you have to select the block and then look at the bar above each panel. Maybe some symbol could be added to the scrollbar.

Right now, it's a little confusing to check which block is being currently reviewed in the merge tool (or on the diff tool). Only colors might not be enough, or, maybe, changing the color on the scroll bar may be the solution.

If the selected changeset removed something and added something else, the result file panel will show the old line with a strikethrough. That's a bit counter-intuitive, IMO, for I want to see the actual result (which wouldn't include any removed lines).

I'm doing some heavy duty Matlab refactoring, which is a realm of development that often takes place in realms outside of widely accepted software practices (http://programmers.stackexchange.com/questions/43733/who-organizes-your-matlab-code?rq=1). Having this sort of language aware difference checker would have greatly aided all the cross file, cleanup, rearchitecting refactoring I had to conduct.

I use a VM and my license keeps getting made invalid and I have to raise a support ticket to get it fixed. This makes it unusable for me

When doing a manual merge you might be experimenting, so undoing a line change is invaluable.

SemanticMerge opens up files one at a time when I issue git difftool/mergetool commands. This is a pain since with several files when the context is important and moving back and forth between files is often necessary. Git's option --dir-diff was designed to address this - but it doesn't work with SemanticMerge. Beyond Compare supports this and as such I find myself using it more, much as I prefer the SemanticMerge UI.

Nemerle is a multi-paradigm programming language for .NET platform

While you're at it with adding C++ support why not go a bit further and support C++/CLI code? We use both regularly and would love to use semanticmerge with all our code.

When viewing a text diff of the current and previous versions of a file it'd be nice to be able to easily move changes from the previous file back into the current one.

It's not necessarily to work just with github.com pull requests. I'd like to see all code changes between two branches in one window to review my/colleagues changes.

Support Swift for all us iOS and OS X devs.

When I go to diff several changes from a single changelist in perforce, I can launch a diff on the whole changelist.

Currently this shows up as several windows, which is a little unwieldy to switch between easily - can semanticmerge be set to have a tabbed interface for multiple diffs / merges, much like beyond compare currently does?

On Windows, the close button ("x") does not extend all the way to the top right corner. This can cause me to "miss" the button and just click on the title bar. Can you enlarge this button to extend all the way to the top-right pixel. This is generally a good UI practice. Thanks!

Currently semantic differences are grouped by type (added, changed, deleted), but sometimes it's not preferred way to see changes. Sometimes preferred way to see changes is in order they are located in file.

When reviewing changes it would be useful to revert modified blocks in the code (as you can do in p4merge for instance).

For example Cp-1251 (Cyrrilic, Windows-1251) wasn't autodetected