git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] difftool falls back to normal diff when used during merge resolution

From
David Aguilar <davvid@gmail.com>
Date
Nov 28, 2011, 11:16 UTC
Message-ID
<2814991420316381881@unknownmsgid>
In-Reply-To
<CAHWJSOSB768hWsNqrR559wef3-k_yZ=TjS_mxfj3TxXdgwm5iQ@mail.gmail.com>
On Nov 27, 2011, at 10:09 AM, Jakub Turski <yacoob@gmail.com> wrote:
Show 16 quoted lines
> Hello there,
>
> Just found this behavior, and after a chat on IRC it looks to me like
> an actual bug. I have 'git difftool' configured to use vimdiff - and
> it worked fine. Despite that config, git still falls back to plain
> diff when I launch difftool mid-way through merge conflict resolution.
>
> Here's a reproducable testcase (w/ version 1.7.7.3)
>
> $ mkdir a; cd a; git init; echo A>A; git add A; git commit -m A; git
> branch alt; echo AA>A; git commit -am AA; git checkout alt; echo B>A;
> git commit -m B; git commit -am B; git checkout master; git merge alt;
> git difftool -t vimdiff A
>
> Results:
> http://pastie.org/2929336

I think this is an unfortunate case where the implementation leaks into the user experience.

I haven't checked, but I'm pretty sure this is because GIT_EXTERNAL_DIFF has no affect when the conflicts exist.

git mergetool can be used in this situation.

We could do a check up front in difftool to see whether conflicts exist and exit with an error message. The difftool script is quite small and basically a very thin wrapper around git diff, though, so I do hesitate before making it more complicated.

anyways, try "git mergetool".
-- 
            David
Previous: Jakub Turski
Message 2 of 2 in “[BUG] difftool falls back to normal diff when used during merge resolution”
  1. Jakub TurskiNov 27, 2011
  2. David AguilarNov 28, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.