49 results found
-
C++ support
It would be great to have C++ support
634 votesWe have included C++ support in 2.0.99.0!!!
Enjoy!
-
OS X... please...
"Our goal is to develop GUIs for MacOS X next and later Linux, depending on what users demand… so it is your call! :-)"
This is my call! :)
510 votes -
Linux... please...
I was really excited about the project but disappointing when i realized I couldn't use it on Linux.
421 votes -
F# Support
C#, F#, and Javascript are the 3 languages I use at work so having F# support would be awesome!
243 votesWe have a community contributed parser! :-)
https://github.com/sageserpent-open/SemanticMergeFSharpPlugin
-
Support merging across files
Right now the samples on the website about splitting up a class are a bit unrealistic since they all include splitting the class up but keeping it all in the same file. In reality, we often move code to different files and still want to merge. SemanticMerge will be revolutionary if it can solve this problem.
236 votesDear all,
We are happy to announce that we implemented your request of cross-file semantic merging.
It is really awesome and since strong git integration is a must, it is part of our new product: gmaster a full-featured Git client based on Semantic tech.
You can download it here:
And you can watch a video of cross-file merging in action here:
Enjoy!
-
Delphi/Pascal support please...!
Need support for Delphi Object Pascal pretty pretty please...!!
179 votesDone!
Please check http://www.plasticscm.net/index.php?/topic/1857-delphi-parser-development/
-
C support
The C programming language is it's own thing! And implementing it would be way easier than C++, with all its object-orientation and template metaprogramming and multiple inheritances! Let's make this happen!
173 votesDONE! It is available to download at www.semanticmerge.com :-)
-
Add a diff view when there is a merge conflict
When there is changes in source and destination, you could see :
- the code of the source and the diff with the source.
- the code of the destination and the diff with the destination.
The problem, is that you can't understand easily the problem without opening the first diff, then the second diff. And perhaps reopen the first diff,...
A better way to understand the merge problem would be to have in the right pane a view that display the "diff view" that show a typical diff with lines differences
123 votesA diff view within the SemanticMerge!
-
PHP Please!
Please add support for PHP.
120 votesWe have included PHP support in 2.0.135.0!!!
Enjoy!
-
C# 5 support
When comparing C# 5 files with async and await keywords, an error dialog pops up saying "The following parsing errors have been found, the trees could be inconsistent".
The parsing errors are on functions that use the async / await keywords.
Expected bahaviour: C# 5 has been out for a while now, so should be correctly parsed.
101 votesC# 5 support on Windows and Mac! Linux will join soon.
-
Idea: Autodetect syntax highlighting based on file extension
The syntax highlighting could be inferred from the file extension if present.
Example: .cs, .java, .h, .c, .cpp would default to the C# / Java / C option.
99 votes -
Keyboard shortcuts
To be able to use keyboard to go over differences or do the merge. The need to use a mouse makes the process much longer
77 votesWe have just launched a new release of SemanticMerge, check it out!
- Accelerator keys have been implemented for every button.
- Use the keyboard to go over differences.
- Current window can be closed using the Esc key.
And we will improve more in conflicts for next release too ;)
-
Automatic installation of semantic merge for svn, git,tfs, ....
Can you install automatically the semantic merge tool on install or in a option dialog.
CodeCompare from devart does this already so it's much faster to setup and work with.
66 votesA new release (1.0.72.0 – Hamm) has been publish with support for this! Check it out!
-
44 votes
It has already been resolved, check the site at http://www.semanticmerge.com/linux/index.html
-
Ignore blank lines
Between methods different developers have different standards for number of blank lines (1 is correct, others use 2 or more). These show up in diffs, but they are not semantic differences.
42 votesNew SemanticMerge able to skip differences where only EOLs and indentation changed.
Check it out!
http://blog.semanticmerge.com/2014/04/new-semanticmerge-1061-is-out.html
-
Refresh button
Many other diff tools allow you to refresh/reload code (ie: if you make small changes and you'd like to re-diff).
Currently, you need to close and re-open the tool.
38 votesA new button (“restart diff”) in semantic diff tool is available to allow you to refresh or reload the code.
-
c# 7 support
Please add support for c# 7
33 votesA new release (2.0.118.0 – Doraimon) has been publish with support for this! Check it out!
-
Personal type of licensing for SemanticMerge
Maybe this is early question... But, when i requested license for beta , i've noticed "Valid for machine" line below the license code key. Will it remain for release? We live in era when we work everywhere and everytime, and not tied to particular machine. So personal licensing would be much more relevant and attractive for users.
32 votesWell, the Semantic licenses are tied to a machine, but we gave as many extra lics for extra machines as needed to the people purchasing Semantic… so it shouldn’t be a big issue anymore.
-
Semantic Merge needs to be smarted about unimportant changes
I think that when there are no changes but in whitespace (not within string literals of course) SM shouldn't show that there are any difference.
28 votesNew SemanticMerge able to skip format conflicts.
Check it out!
http://blog.semanticmerge.com/2014/05/skip-format-conflicts-with-new.html
-
Merge command line parameter to ignore white space or tabs in front of lines
Lets say I have a C# file that I have auto formatted to use spaces. Some other developer has auto formatted it to use tabs. This shows up as a merge conflict. I have to view the diff and choose "Ignore White Space and EOL" and semantic merge then marks it as "Resolved".
It would be nice if semantic merge always did this or at least provided a command line switch that lets us turn this on if we want to. This way I can add it to my .gitconfig file if I know I will be working in a…
27 votesNew SemanticMerge able to skip differences where only EOLs and indentation changed.
Check it out!
http://blog.semanticmerge.com/2014/04/new-semanticmerge-1061-is-out.html
- Don't see your idea?