Skip to content

Conversation

czarkoff
Copy link
Contributor

The WinMerge preset in the application opens WinMerge in a 3-way merge configuration with theirs version on the left, ours in the middle and raw conflict file on the right:
image
This seems to be aligned with the advice on the internet, but provides suboptimal user experience. The fact that WinMerge doesn't have keyboard shortcuts to operate on the middle pane doesn't help either.

Winmerge supports opening conflict files directly, and for them it creates a 2 pane UI with theirs version on the left and ours on the right:
image
Ours is what is eventually saved when the conflict is resolved.

To me the latter appears to be much more useful, though I can see how someone may want to keep both ours and theirs in their view for the whole conflict resolution session.

@czarkoff czarkoff changed the base branch from master to develop November 17, 2024 14:07
@love-linger love-linger self-assigned this Nov 18, 2024
@love-linger love-linger added the enhancement New feature or request label Nov 18, 2024
@love-linger love-linger merged commit f4618af into sourcegit-scm:develop Nov 18, 2024
@czarkoff czarkoff deleted the WinMerge branch November 18, 2024 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants