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

[PATCH] use get_merge_tool_path() also in is_available() to honor settings

From
MGMichael Schindler via GitGitGadget <gitgitgadget@gmail.com>
Date
Jun 7, 2021, 20:47 UTC
Message-ID
<pull.1032.git.git.1623098845733.gitgitgadget@gmail.com>
From: Michael Schindler <michael@compressconsult.com>

fix the is_available test used in git mergetool --tool-help or git difftool --tool-help or to check the list of tools available when no tool is configured/given with --tool

symtoms: the actual tool running run_merge_tool () considers the difftool. "$merge_tool".path and mergetool."$merge_tool".path and if configured honors these. See get_merge_tool_path () in git-mergetool--lib.sh If not set use fallback: translate_merge_tool_path "$merge_tool".

The is_available () just uses translate_merge_tool_path "$merge_tool".

repo 1: Configure an invalid path in mergetool."$merge_tool".path for a tool of your choice. You will be informed that the tool is available, but when trying to use it will not be found because the invalid configured path is used.

repo2: Install a tool of your choice on a nonstandard place (e.g. rename the program) and configure mergetool."$merge_tool".path for this tool. You will be informed that the tool is not available (because not found on standard place), but when trying to run it will work.

This fix will make the information consistent by using get_merge_tool_path() also in is_available()

Signed-off-by: Michael Schindler <michael@compressconsult.com>
---
    use get_merge_tool_path() also in is_available() to honor settings
    
    fix the is_available() used in git mergetool --tool-help or git difftool
    --tool-help or used to check the list of tools available when no tool is
    configured/given with --tool
    
    symtoms: the actual tool running run_merge_tool () considers the
    difftool."$merge_tool".path and mergetool."$merge_tool".path and if
    configured honors these. See get_merge_tool_path () in
    git-mergetool--lib.sh If not defined use fallback:
    translate_merge_tool_path "$merge_tool".
    
    The is_available () just uses translate_merge_tool_path "$merge_tool".
    
    repo 1: Configure an invalid path in mergetool."$merge_tool".path for a
    tool of your choice. You will be informed that the tool is available,
    but when trying to use it it will not be found because the invalid
    configured path is used.
    
    repo2: Install a tool of your choice on a nonstandard place (e.g. rename
    the program) and configure mergetool."$merge_tool".path for this tool.
    You will be informed that the tool is not available (because not found
    on standard place), but when trying to run it will work.
    
    This fix will make the information consistent by using
    get_merge_tool_path() also in is_available()
    
    Signed-off-by: Michael Schindler michael@compressconsult.com
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1032%2Fmichaelcompressconsult%2Fmergetoollib_is_available-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1032/michaelcompressconsult/mergetoollib_is_available-v1
Pull-Request: https://github.com/git/git/pull/1032
 git-mergetool--lib.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh
index 542a6a75eb3c..8b946e585d7f 100644
--- a/git-mergetool--lib.sh
+++ b/git-mergetool--lib.sh
@@ -18,7 +18,7 @@ mode_ok () {
 }
 
 is_available () {
-	merge_tool_path=$(translate_merge_tool_path "$1") &&
+	merge_tool_path=$(get_merge_tool_path "$1") &&
 	type "$merge_tool_path" >/dev/null 2>&1
 }
 

base-commit: c09b6306c6ca275ed9d0348a8c8014b2ff723cfb
-- 
gitgitgadget
Next: Junio C Hamano
Message 1 of 4 in “use get_merge_tool_path() also in is_available() to honor settings”
  1. use get_merge_tool_path() also in is_available() to honor settingsMichael Schindler via GitGitGadget, Jun 7, 2021
  2. Junio C HamanoJun 8, 2021
  3. David AguilarAug 30, 2021
  4. Adam DinwoodieAug 31, 2021

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.