Setup p4merge as a visual diff and merge tool for git

p4merge4git.md

Download and install p4merge

• Download the perforce visual tool suite from here: http://www.perforce.com/perforce/downloads/index.html
• Copy only the p4merge.app file into your /Applications/ directory

Setup p4merge as a visual mergetool

$ git config --global merge.tool p4mergetool
$ git config --global mergetool.p4mergetool.cmd \
"/Applications/p4merge.app/Contents/Resources/launchp4merge \$PWD/\$BASE \$PWD/\$REMOTE \$PWD/\$LOCAL \$PWD/\$MERGED"
$ git config --global mergetool.p4mergetool.trustExitCode false
$ git config --global mergetool.keepBackup false

Setup p4merge as a visual diff tool

$ git config --global diff.tool p4mergetool
$ git config --global difftool.p4mergetool.cmd \
"/Applications/p4merge.app/Contents/Resources/launchp4merge \$LOCAL \$REMOTE"

Using p4merge to resolve conflicts

When you run into a conflict when merging simply run:

$ git mergetool

• You will be prompted to run "p4mergetool", hit enter and the visual merge editor will launch.
• Using the merge tool you can resolve the conflict and then save the file.
• After you exit the merge tool take a look back at your terminal. You will be asked if the merge was successful, choose yes if all is well or no if you need to start over.
• This prompting is happening because the "trustExitCode" option is turned off. Personally I always like to be asked, but you can have git just trust the exit code from the merge tool.

You should add How To for Windows and Linux.

Are you sure about order in
"/Applications/p4merge.app/Contents/Resources/launchp4merge $PWD/$BASE $PWD/$REMOTE $PWD/$LOCAL $PWD/$MERGED"

Looks like it should be
"/Applications/p4merge.app/Contents/Resources/launchp4merge $PWD/$BASE $PWD/$LOCAL $PWD/$REMOTE $PWD/$MERGED"

Correct me if I'm wrong

I guess you are right camobap

It works. Thanks!

@zzba9000: The GIT docs explain how to hook GIT up with p4merge/p4diff:

http://git-scm.com/book/en/Customizing-Git-Git-Configuration

I made a launcher script that irons things out when using Git + P4Merge, I explain the setup in a blog post http://pempek.net/articles/2014/04/18/git-p4merge/

Hope that helps

I think your need quotation marks " surround $XX in case white spaces in filenames.

tford!

Windows p4merge setup git mergetool:
https://gist.github.com/mikemichaelis/4f6d62a03300a24e97c1d19b9413371e

Thanks for sharing!

These instructions don't actually work, at least not on Mac OS X 10.12 or 10.13.

Use this URL under the heading: "External Merge and Diff Tools"

This instruction is obsolete and doesn't work.

Hey, guys. I would like to share my working p4merge(2018.2-1666551) setup on macOS Mojave from both https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration and https://community.perforce.com/s/article/2848

1. $ brew cask install p4merge
2. $ sudo vim /usr/local/bin/extMerge and add below lines:

#!/bin/sh
/Applications/p4merge.app/Contents/MacOS/p4merge $*

from preforce, the /Applications/p4merge.app/Contents/Resources/launchp4merge is not working on me. However, above 'none-shim' method can bring up p4merge windows app. So weird.

3. $ sudo vim /usr/local/bin/extDiff and add below lines:

#!/bin/sh  
/usr/local/bin/extMerge "$2" "$5"

4. $ sudo chmod +x /usr/local/bin/extMerge and
   $ sudo chmod +x /usr/local/bin/extDiff

5. my ~/.gitconfig

[merge]
	tool = extMerge
	stat = true
[mergetool "extMerge"]
	cmd = extMerge "$BASE" "$LOCAL" "$REMOTE" "$MERGED"
	keepBackup = false
	keepTemporaries = false
	trustExitCode = false
	prompt = false
[diff]
	external = extDiff
	renames = copies
	mnemonicprefix = true
[difftool "extDiff"]
	cmd = extDiff "$LOCAL" "$REMOTE"
	keepBackup = false
	keepTemporaries = false
	trustExitCode = false
	prompt = false

That's it. I hope these works on your machine.

👍

@jenhsun Phew, finally it works, thanks a lot sir! For some reason after update to Mojave p4merge started asking me to choose files to merge manually, it just drove me crazy but your config works fine!

@jenhsun This gets me closer but that doesn't seem to escape spaces in the filepath, leading to p4merge complaining about too many arguments.

I've tried the following:

cmd = mymerge ${BASE} ${LOCAL} ${REMOTE} ${MERGED}
# and this one fails too
cmd = mymerge "${BASE}" "${LOCAL}" "${REMOTE}" "${MERGED}"

But p4merge fails with the same error on both. How do I make sure spaces are escaped?

EDIT:

I ended up having to explicitly enumerate the arguments in the shell script, the $* does not seem to carry the quotes/spaces over.

This is fine, since I never expect the number of arguments to change.

#!/bin/sh

/Applications/p4merge.app/Contents/MacOS/p4merge "$1" "$2" "$3" "$4"

Not sure why it stops working in Mac OSX Mojave. But I had to move from the shim to the app so just doing this worked for me:

[mergetool "p4merge"]
  cmd = /Applications/p4merge.app/Contents/MacOS/p4merge "$BASE" "$LOCAL" "$REMOTE" "$MERGED"

It used to be

[mergetool "p4merge"]
  cmd = /Applications/p4merge.app/Contents/Resources/launchp4merge "\"$PWD/$BASE\"" "\"$PWD/$REMOTE\"" "\"$PWD/$LOCAL\"" "\"$PWD/$MERGED\""

Versions:

• git version 2.19.1
• Mojave 10.14 (18A391)
• Rev. P4Merge/MACOSX1013X86_64/2018.3/1706936

I guess you are right camobap

why not correct it then?

I guess you are right camobap

why not correct it then?

+1

if you want git to skip prompting for confirmation to open every single file do this:
git config --global --add difftool.prompt false

Thanks!

After I resolve a merge, I get /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git-mergetool--lib: line 128: 8522 Segmentation fault: 11 /Applications/p4merge.app/Contents/Resources/launchp4merge $PWD/$BASE $PWD/$REMOTE $PWD/$LOCAL $PWD/$MERGED. How can I fix this?

merge config given at https://apple.stackexchange.com/a/346038/267749 worked instead for me.
P4Merge version -> Rev. P4Merge/MACOSX1015X86_64/2020.1/1966006
Git version -> git version 2.24.3 (Apple Git-128)

Most recent version of git already have included configuration for P4Merge. The only thing you need to do on a Mac is:

# setup p4merge as the default difftool
git config --global diff.tool p4merge

# setup p4merge as the default mergetool
git config --global merge.tool p4merge

# Define the path to P4merge launcher.
git config --global mergetool.p4merge.path /Applications/p4merge.app/Contents/Resources/launchp4merge

Note the p4merge instead of p4mergetool. This will setup P4Merge with the correct launch arguments. This was tested with:

• P4Merge/MACOSX1015X86_64/2020.3/2060285
• MacOS Catalina 10.15.7 (19H114)
• git version 2.30.0 (also tested with git version 2.24.1)

At the end, the only required configuration related to P4 you need in your .gitconfig (excluding your personal preferences) should be:

[diff]
  tool = p4merge
[merge]
  tool = p4merge
[mergetool "p4merge"]
  path = /Applications/p4merge.app/Contents/Resources/launchp4merge

Works perfectly for me, @louim, thanks 👍

Thank you @louim, works like a charm 👍

Does it prompts you for files when you run git diff-tool master..develop for example?
For me, it does and shouldn't be like that.

There is a window that asks about the paths, but there is also a confirmation dialog that asks if it is OK for an Applescript to be run, and when you approve it to run the script (which you only have to do once), then the path window disappears and the merge opens as expected. I installed via homebrew.

Still works perfectly in 2023. macOS Ventura