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

Re: Running vimdiff in read-only mode with git-difftool?

From
David Aguilar <davvid@gmail.com>
Date
May 18, 2009, 05:42 UTC
Message-ID
<20090518054224.GA32259@gmail.com>
In-Reply-To
<9e00fd550905172201n6c95dc1bia48c9ac25d8ec98f@mail.gmail.com>
On Sun, May 17, 2009 at 10:01:02PM -0700, Nick Welch wrote:
Show 8 quoted lines
> 
> According to the git-difftool manpage, what I'm trying to do
> should work:
> 
>   Instead of running one of the known diff tools,
>   git-difftool can be customized to run an alternative
>   program by specifying the command line to invoke in a
>   configuration variable difftool.<tool>.cmd.

Custom difftool.<tool>.cmd settings only work for custom (i.e. alternative/non-built-in) tools.

If you rename that to something like "myvimdiff" (or anything != "vimdiff") then it'll work as expected.

I wouldn't be opposed to a patch making {diff,merge}tool.<tool>.cmd work for built-in tools as well as long as it had a testcase and didn't end up making the code unnecessarily complex.

-- 
	David
Previous: Nick WelchNext: David Aguilar
Message 2 of 4 in “Running vimdiff in read-only mode with git-difftool?”
  1. Nick WelchMay 18, 2009
  2. David AguilarMay 18, 2009
  3. David AguilarMay 18, 2009
  4. Nick WelchMay 18, 2009

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.