Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here is how I fixed it:</p> <p>Created <code>/usr/local/bin/opendiff-w</code> filled with:</p> <pre><code>#!/bin/sh # opendiff returns immediately, without waiting for FileMerge to exit. # Piping the output makes opendiff wait for FileMerge. opendiff "$@" | cat </code></pre> <p>Then ran the command: <code>sudo chmod +x /usr/local/bin/opendiff-w</code></p> <p>Then edited <code>~/.hgrc</code> with the following addition:</p> <pre><code>[extdiff] cmd.interdiff = hg-interdiff cmd.opendiff = opendiff-w [merge-tools] filemerge.executable = /usr/local/bin/opendiff-w filemerge.args = $local $other -ancestor $base -merge $output [extensions] extdiff = </code></pre> <p>Then I ran the following command to check wether it worked: <code>hg opendiff</code></p> <p>However, I got the following error:</p> <pre><code>exception raised trying to run FileMerge: launch path not accessible </code></pre> <p>In order to fix it I ran the following command:</p> <pre><code>sudo /usr/bin/xcode-select -switch /Applications/Xcode.app/Contents/Developer/ </code></pre> <p>This should now work and open up FileMerge.</p> <p>====================================================================</p> <p>If you're using TorsoiseHg for Mac, the only thing you need to do now in order to work with FileMerge is to choose filemerge from the Detected merge/diff tools when the Resolve Conflict window appears and choose Tool Resolve.</p> <p><img src="https://i.stack.imgur.com/8dO44.png" alt="enter image description here"></p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload