You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Happy to help fix this myself, unfortunately I don't know how at the moment. Note that launching diffmerge from finder works fine, but launching from the command line does not.
This is because diffmerge is a symlink to diffmerge.sh which contains this code:
#!/bin/sh
## A little script to make it easier to launch DiffMerge from the command line.
## Install this script into a folder in your path, such as /usr/bin or /usr/local/bin.
##
## Version 4.2.0.697
## Copyright (C) 2003-2013 SourceGear LLC. All Rights Reserved.
##############################################################################
## Change DIFFMERGE_PATH to point to where you installed DiffMerge
DIFFMERGE_PATH=/Applications/DiffMerge.app
## The actual executable is hidden inside the .app bundle.
DIFFMERGE_EXE=${DIFFMERGE_PATH}/Contents/MacOS/DiffMerge
## Launch DiffMerge using the given command line arguments. Use --help for
## additional information or see the man page distributed along with this
## shell script.
exec ${DIFFMERGE_EXE} --nosplash "$@"
which assumes DiffMerge lives in /Applications, and indicates that the developer-supported way to launch diffmerge from the command line is to edit this file. I can think of a few solutions, none of which are great. We could write code that will edit this file after downloading, but that seems too brittle, we could symlink the DiffMerge binary instead of this shell script, but then we miss out on the --nosplash option, or we could just add a caveat telling the user to edit the file, but thats not very automatic. Thoughts?
The text was updated successfully, but these errors were encountered:
Good catch. For the moment, it seems like the best answer would be to link the DiffMerge binary and add a caveats line explaining how to eg configure git to use the --nosplash option.
For a general fix, I think that (instead of a symlink) we would have to write a one-line bash shim that does
exec /full/path/to/the/real/diffmerge.sh "$@"
This same issue came up recently on cycript.rb, and there is at least on other similar case.
I made a pull request to fix this issue, but it introduces another issue. While diffmerge can be invoked from the command line, doing so causes some debug alerts to appear. I haven't been able to figure out why.
Happy to help fix this myself, unfortunately I don't know how at the moment. Note that launching diffmerge from finder works fine, but launching from the command line does not.
This is because
diffmerge
is a symlink todiffmerge.sh
which contains this code:which assumes DiffMerge lives in /Applications, and indicates that the developer-supported way to launch diffmerge from the command line is to edit this file. I can think of a few solutions, none of which are great. We could write code that will edit this file after downloading, but that seems too brittle, we could symlink the DiffMerge binary instead of this shell script, but then we miss out on the
--nosplash
option, or we could just add a caveat telling the user to edit the file, but thats not very automatic. Thoughts?The text was updated successfully, but these errors were encountered: