Skip to content

semanticmerge

semanticmerge

Categories

JUMP TO ANOTHER FORUM

(thinking…)

The merge tool that understands your code

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

49 results found

  1. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →

  2. Add Mercurial configuration documentation

    It would be nice if there was documentation on how to use the tool with Mercurial. See http://mercurial.selenic.com/wiki/MergeToolConfiguration

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →

  3. Separate availability from PlasticSCM

    Seeing as you are already talking about using this with other source control systems, I assume you will have separate pricing & availability from PlasticSCM.

    I always liked the look of XDiff & XMerge, but AFAICT they are only available as part of PlasticSCM. We use subversion & TFS, so there's no way I could purchase PlasticSCM licenses purely to get access to the diff tools!

    Thanks!

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  4 comments  ·  Admin →

  4. SVN please

    Title says it all. I'm hoping that this can be configured with SVN in the future.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Admin →

  5. Gracefully handle diffs on new files from git

    If I run a git difftool on a file that exists now but did not in a previous commit (was created), the destination file does not exist and causes semanticmerge to throw several errors

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  6. Drag and Drop Files

    Something small, I like being able to drag and drop files into the diff tool and into the file selection menu. Sometimes I work in multiple branches of the same code base and drag and drop makes it easy to compare the different versions quickly.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  7. Improve startup performances (under 1s)

    When I'm trying to use it with Visual Studio on my computer for compare task, the startup time is around 10s which is far too long if I want to use it.
    (remark: I'm happy to have only one instance running if needed to speedup time)

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Admin →

  8. Crowd-source your parsing engines

    Everyone seems to want language 'x' supported, you will never keep up, create a framework and host plugin examples on github, this will also allow meta-languages (e.g. creative (ab)use of the C pre-processor) to be supported.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  9. Remember settings between sessions

    When I select Ignore blank lines and/or whitespace, the program does not remember this so I have to set it all over again the next time. This is tiresome and a time waster because the initial diff is useless without the right settings.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  10. External merge tool and diff tool should be persistent and easily configurable from the GUI

    Passing the right parameters and properly escaping for a external tools is tedious and prone to shell expansion.

    The integration of external merge/diff tools with Semanticmerge should be done via the GUI and should be persistent across sessions.

    The GUI should have hints (tooltip or a contextual help button) about the possible names and titles placeholders (i.e.: describe what #sourcefile, #destinationfile, #basesymbolic etc. expand to) so it's easy for users to configure third party tools based on their documentation.

    Extra bonus points if there is a preview text box where the commands entered by the user is expanded to show…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  11. Tutorial for tortoise

    Please provide a configuration tutorial for tortoiseGit ad TortoiseHg.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  12. Semantic Diff Window - option to view source and destination

    Enable the text-diff view right in place with the Semantic Diff Window. Right now, I always have to click "run text diff" every time I want to compare the changes.It would be much easier if I could click on a class or method and it would show me the changes right there on the left side, in two neat windows.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  13. Fix the issues with spaces in the user directory

    If there are spaces in the user directory then you can't merge or diff, which is a pain.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  14. fall back on text-based merge if syntax is not recognised

    you may already do this - but the tool should perform a text based merge if it cannot do a smart merge for a given file.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Admin →

  15. Mergetool options should be sticky and configurable

    It should be possible to set the different merge options in a config file or via the parameters (in mercurial.ini or something like that).

    Running a big merge with a lot of whitespace issues forces me to options> comparison >"ignore EOL and whitespace" hundreds (!) of times as it is not sticky between merges.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  16. Preference needed.

    Preference needed. (Save ignore whitespace settings, set external text compare software, etc.)

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  17. Tutorial for tortoise svn

    Please provide a configuration tutorial for tortoiseSvn

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Admin →

  18. Perforce Support

    I think my team would find this really useful however we use Perforce so support for that would be great!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →

  19. Option to update diff window automatically when selecting different changes

    If I have a set of changes in a few methods, currently I have to select each change and click on the "diff" button to see the diff window at the bottom.

    It would be nice to be able to "Pin" the diff window to the bottom of the screen and have it update automatically as I move through the changes.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  20. Format code to every user's liking and end the endless discussion of how something should be formatted.

    Since there is no semantic difference between different ways of code formatting, there is no point in forcing people to format there code in a certain way. Code could be checked in without formatting and checked out with the formatting that the developer wants. Put an end to the endless code formatting discussions and make tools like StyleCop redundant.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
2
  • Don't see your idea?