I couldn't find information about whether the -solo feature is available in all Beyond Compare versions. At the least I can say that it is available in version 3 for Windows, since that is the version that we're using. This issue does not occur when using the normal difftool (command: git difftool), which is odd and indicates that something must be wrong in either Git or Beyond Compare. On Wed, Sep 10, 2014 at 2:00 AM, David Aguilar <davvid@xxxxxxxxx> wrote: > On Mon, Sep 08, 2014 at 04:36:49PM +0200, R. Klomp wrote: >> Ok great! That indeed fixed the issue. >> Although I still don't understand why it didn't work without -solo.. >> since it didn't work when no instance of Beyond Compare was running as >> well. >> >> There must be something not quite right in either Git or Beyond Compare. >> >> On Mon, Sep 8, 2014 at 3:37 PM, Jim Naslund <jnaslund@xxxxxxxxx> wrote: >> > >> > On Sep 8, 2014 7:39 AM, "R. Klomp" <r.klomp@xxxxxxxxxxxxxx> wrote: >> >> >> >> It seems like there's a bug involving git difftool's -d flag and Beyond >> >> Compare. >> >> >> >> When using the difftool Beyond Compare, git difftool <..> <..> -d >> >> immidiatly shuts down once the diff tree has been created. Beyond >> >> Compare successfully shows the files that differ. >> >> However, since git difftool doesn't wait for Beyond Compare to shut >> >> down, all temporary files are gone. Due to this it's impossible to >> >> view changes made inside files using the -d flag. >> >> >> >> I haven't tested if this issue also happens with other difftools. >> >> >> >> I'm using the latest versions of both Beyond Compare 3 (3.3.12, Pro >> >> Edition for Windows) and Git (1.9.4 for Windows). >> >> >> >> >> >> Thanks in advance for your help! >> > >> > I see the same behavior. For me it had something to do with the diff opening >> > in a new tab in an existing window. Adding -solo to difftool.cmd will make >> > beyond compare use a new window which fixes the issue for me. > > Interesting. Would it be worth changing difftool to use -solo by default, or > are there any downsides to doing so? > > Is -solo a new feature that only exists in new versions of beyond compare? > I would be okay saying that the user should use a fairly new version. > > Can we rely on -solo being available on all platforms? > If so, I'd be okay with changing the default if there are no other downsides. > > The --dir-diff feature is not the only one that needs this blocking behavior. > Does this issue also happen in the normal difftool mode without -d? > -- > David -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html