120 results found
-
Resolved conflicts shouldn't show on the scroll bar
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.
4 votes -
improve C parser for comments and report comment changes
please run a simple diff with semanticmerge
It will tell you that the include <...> has been changed, not the comment4 votes -
semantic merge for better delta code review
how awesome would it be if you join forces with another tool vendor and create a full integration of your semantic diff (including moving things from one file to another) and a tool that helps during code reviews and tracks findings...
finally one could focus on real changesps: plastic scm is missing on their list of integrations
https://smartbear.com/product/collaborator/overview/4 votes -
Support for blank comparison
Would be nice if you could start a blank comparison and then copy and paste code from different sources without saving to file like Meld.
4 votes -
New Diff dialog when you've already got the tool open
Basically, when running the diff tool outside of the IDE if you want to compare another set of diffs, you'll nee to close the semantic merge tool and reopen it.
Would be great if we could be presented with the "welcome dialog" you see when you open the app for the first time.
3 votes -
Machine-specific location for storing license keys.
I usually install my programming tools into a bin directory in my dropbox profile, so that it's replicated across my machines. This is a problem with SM, which tells me my license is corrupt any time I switch boxes.
3 votes -
FreePascal
Free pascal support please ;-)
3 votes -
Update your Fedora packages for Fedora 20
The packages here don't work on Fedora 20:
http://www.semanticmerge.com/linux/#fedora
I looks like you just need to recompile against a newer version of libtiff.
3 votes -
Visual Basic/VBA
Add support for Visual Basic/VBA
3 votes -
3 votes
-
Make showing removed blocks from the Result File optional
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).
3 votes -
Debian packages are signed with an expired key
Currently (for some time now) when running 'update' in aptitude the following error is reported:
A: GPG error: https://www.semanticmerge.com ./ Release: The following signatures are not valid: KEYEXPIRED 1442157655
Of course, this has nothing to do with 'aptitude'.
A new key needs to be provided and packages need to be signed with that key.
The way Debian and Ubuntu do this is to have a separate package which is signed with the old key, and, when needed, delivers the new keys, then, after that package is available, the new key can be used for signing.
3 votes -
3 votes
-
Support for merging NuGet packages.config files
NuGet package files are simple XML files, and the merge procedure should be reasonably simple too.
Packages are keyed by ID, so if there's a collision based on the ID, take the package reference with the highest version number.
If the two sources include unique packages, the result should be the union of the two.
3 votes -
Diff control for .Net application.
Maybe many will is interesting to compare files in your application. Is it possible to create a new product in the form of control for the .Net applications?
I apologize if this is a silly suggestion, but the market I have not seen something like that.
Thank you.3 votes -
Support for Perl 5 and 6
Show how smart you are by support Perl. It is said that only Perl can understand Perl...
3 votes -
Add possibility to compare Remote and Local files during merge
Currently, during a 3-way merge, the shown differences are always between Remote/Base and Local/Base.
It would be great to have the possibility of also showing the differences between Remote/Local.
Why? Sometimes the Remote and Local files are exactly the same and since the differences are marked on them when compared to Base they seem to be very different to each other. We have then to open or copy/paste both Remote and Local files on a file editor and then compare them, to see that they are exactly the same.
This is quite common, because when we use squash in Git…
3 votes -
Show differences highlighted also on the result file
Currently, during a 3-way merge, the individual differences are marked only on the Remote, Base and Local files.
On the Result file, it is only shown the main change (line deleted or added), the individual changes are not shown. For example, if you rename a word in one line, on the 3 source files you have that work highlighted, however, on the result file, it's not highlighted, which makes it hard to see what the difference was.
This would be very useful when solving merge conflicts, because then we could see the differences clearly with the changes on top of…
3 votes -
Rust support
Rust is a young but promising language. Having semantic merge would be awesome.
3 votes -
Allow external parsers to be configured extension
Semantic Merge allows for external parsers but currently it only allows for one, making the adoption of using them very limited, when you are using more than one non-supported language. I would like it if Semantic Merge could support configuring external parsers by extensions they handle.
3 votes
- Don't see your idea?