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

Re: [PATCH v1 10/11] git-gui: improve worktree discovery

From
Johannes Sixt <j6t@kdbg.org>
Date
May 16, 2026, 08:16 UTC
Message-ID
<8b8feffa-1651-41aa-ac76-d2721d656b45@kdbg.org>
In-Reply-To
<20260514143322.865587-11-mlevedahl@gmail.com>
Am 14.05.26 um 16:33 schrieb Mark Levedahl:
Show 15 quoted lines
> git gui's worktree discovery needs update based upon prior work in this
> series. In the normal case, all information we need comes directly from
> git rev-parse (--show-toplevel, and --show-prefix). Should this work, we
> have a valid worktree and all git gui commands can run.
> 
> If not, we need to consider:
> - if GIT_DIR or GIT_WORK_TREE are in the environment, just stop as we
>   the input configuration was wrong, the user must fix that.
> - if we have a browser or blame subcommand, no worktree is needed so
>   git-gui can run without.
> - using the git repository's parent is a valid worktree (if possible),
>   restoring prior behavior.
> 
> The current directory should be either the root of the worktree, if one
> is found, or the top-level of the git repository.

I disagree in the case where no working tree is found. Then there is no point in changing the current directory.

> 
> Make it so. Also, make worktree discover directly follow repository
> discovery, reducing the locations that might need error trapping to
> catch configuration issues.
Good!
> 
> Signed-off-by: Mark Levedahl <mlevedahl@gmail.com>

BTW, please make the subject line more descriptive. The word "improve" does not convey anything of importance.

Show 18 quoted lines
> ---
>  git-gui.sh | 56 ++++++++++++++++++++++--------------------------------
>  1 file changed, 23 insertions(+), 33 deletions(-)
> 
> diff --git a/git-gui.sh b/git-gui.sh
> index e326401..3a83dd5 100755
> --- a/git-gui.sh
> +++ b/git-gui.sh
> @@ -1173,6 +1173,28 @@ if {[catch {
>  	}
>  }
>  
> +# find worktree, continue without if not required
> +if {[catch {
> +	set _gitworktree [git rev-parse --show-toplevel]
> +	set _prefix [git rev-parse --show-prefix]
> +	cd $_gitworktree
> +} err]} {

We have three commands, each with their own possible failure sources. One of the outcomes of an error is that we proceed anyway. I think that this is incorrect if the 'cd' fails: we must not proceed if it fails. Therefore, we must handle its failure separately.

Show 7 quoted lines
> +	if {[is_gitvars_error $err]} {
> +		exit 1
> +	}
> +	set _gitworktree {}
> +	set _prefix {}
> +	if {[is_enabled bare]} {
> +		cd $_gitdir

Why change the directory here? If we run `git gui browser master dir` we do not want to change the directory in an uncontrolled manner. The argument parser will want to check for the existence of files, and then we do not want to operate from a random directory.

Also, I think that the check must be for [is_bare] and not [is_enabled bare].

Show 12 quoted lines
> +	} elseif {![is_parent_worktree]} {
> +		catch {wm withdraw .}
> +		error_popup [strcat [mc "Cannot use bare repository:"] "\n\n" $_gitdir]
> +		exit 1
> +	}
> +}
> +
> +# repository and worktree config are complete, export them
> +set_gitdir_vars
>  
>  # Use object format as hash algorithm (either "sha1" or "sha256")
>  set hashalgorithm [git rev-parse --show-object-format]

This moves code around. In particular, we see load_config and apply_config in the context below, which now happens only after these calls. How certain are we that these have no effect on the code that runs now earlier?

Show 49 quoted lines
> @@ -1189,37 +1211,8 @@ if {$hashalgorithm eq "sha1"} {
>  load_config 0
>  apply_config
>  
> -set _gitworktree [git rev-parse --show-toplevel]
>  
> -if {$_prefix ne {}} {
> -	if {$_gitworktree eq {}} {
> -		regsub -all {[^/]+/} $_prefix ../ cdup
> -	} else {
> -		set cdup $_gitworktree
> -	}
> -	if {[catch {cd $cdup} err]} {
> -		catch {wm withdraw .}
> -		error_popup [strcat [mc "Cannot move to top of working directory:"] "\n\n$err"]
> -		exit 1
> -	}
> -	set _gitworktree [pwd]
> -	unset cdup
> -} elseif {![is_enabled bare]} {
> -	if {[is_bare]} {
> -		catch {wm withdraw .}
> -		error_popup [strcat [mc "Cannot use bare repository:"] "\n\n$_gitdir"]
> -		exit 1
> -	}
> -	if {$_gitworktree eq {}} {
> -		set _gitworktree [file dirname $_gitdir]
> -	}
> -	if {[catch {cd $_gitworktree} err]} {
> -		catch {wm withdraw .}
> -		error_popup [strcat [mc "No working directory"] " $_gitworktree:\n\n$err"]
> -		exit 1
> -	}
> -	set _gitworktree [pwd]
> -}
> +# Derive a human-readable repository name
>  set _reponame [file split [file normalize $_gitdir]]
>  if {[lindex $_reponame end] eq {.git}} {
>  	set _reponame [lindex $_reponame end-1]
> @@ -1227,9 +1220,6 @@ if {[lindex $_reponame end] eq {.git}} {
>  	set _reponame [lindex $_reponame end]
>  }
>  
> -# Export the final paths
> -set_gitdir_vars
> -
>  ######################################################################
>  ##
>  ## global init
-- Hannes
Previous: Johannes SixtNext: Johannes Sixt
Message 60 of 134 in “git-gui: handle bare repo or missing worktree”
  1. git-gui: handle bare repo or missing worktreeShroom Moo, Apr 21, 2026
  2. Johannes SixtApr 29, 2026
  3. 1/1 git-gui: protect rev-parse --show-toplevel callShroom Moo, Apr 29, 2026
  4. Shroom MooApr 29, 2026
  5. Mark LevedahlApr 29, 2026
  6. 1/1 git-gui: handle missing worktree and separated gitdirShroom Moo, Apr 30, 2026
  7. Mark LevedahlApr 30, 2026
  8. Shroom MooMay 1, 2026
  9. 1/1 git-gui: handle missing worktree and separated gitdirShroom Moo, May 1, 2026
  10. Johannes SixtMay 1, 2026
  11. Mark LevedahlMay 1, 2026
  12. Mark LevedahlMay 2, 2026
  13. Johannes SixtMay 3, 2026
  14. 1/1 git-gui: restructure repository startupShroom Moo, May 4, 2026
  15. Mark LevedahlMay 4, 2026
  16. Mark LevedahlMay 5, 2026
  17. Johannes SixtMay 6, 2026
  18. Johannes SixtMay 6, 2026
  19. Mark LevedahlMay 6, 2026
  20. Johannes SixtMay 6, 2026
  21. Mark LevedahlMay 6, 2026
  22. 0/3 git-gui: robustify startup and fix environment handlingShroom Moo, May 6, 2026
  23. 2/3 git-gui: disable gitk visualization when no worktree availableShroom Moo, May 6, 2026
  24. 1/3 git-gui: restructure repository startupShroom Moo, May 6, 2026
  25. 3/3 git-gui: handle GIT_DIR and GIT_WORK_TREE earlyShroom Moo, May 6, 2026
  26. Mark LevedahlMay 7, 2026
  27. Mark LevedahlMay 7, 2026
  28. Aina BootMay 9, 2026
  29. Shroom MooMay 9, 2026
  30. 0/3 git-gui: robustify startup and fix environment handlingShroom Moo, May 9, 2026
  31. 1/3 git-gui: restructure repository startupShroom Moo, May 9, 2026
  32. 3/3 git-gui: handle GIT_DIR and GIT_WORK_TREE earlyShroom Moo, May 9, 2026
  33. 2/3 git-gui: disable gitk visualization when no worktree availableShroom Moo, May 9, 2026
  34. Mark LevedahlMay 14, 2026
  35. 00/11 Improve git gui operation without a worktreeMark Levedahl, May 14, 2026
  36. 01/11 git-gui: allow specifying path '.' to the browserMark Levedahl, May 14, 2026
  37. 02/11 git-gui: refactor browser / blame argument parsingMark Levedahl, May 14, 2026
  38. 04/11 git-gui: put choose_repository::pick in a procMark Levedahl, May 14, 2026
  39. 05/11 git-gui: use --absolute-git-dirMark Levedahl, May 14, 2026
  40. 03/11 git-gui: guard set/unset of GIT_DIR and GIT_WORK_TREEMark Levedahl, May 14, 2026
  41. 06/11 git gui: GIT_DIR / GIT_WORK_TREE make any discovery error fatalMark Levedahl, May 14, 2026
  42. 07/11 git-gui: use rev-parse exclusively to find a repositoryMark Levedahl, May 14, 2026
  43. 08/11 git-gui: simplify [is_bare] to report if a worktree is knownMark Levedahl, May 14, 2026
  44. 09/11 git-gui: support using repository parent dir as a worktreeMark Levedahl, May 14, 2026
  45. 10/11 git-gui: improve worktree discoveryMark Levedahl, May 14, 2026
  46. 11/11 git-gui: add gui and pick as explicit subcommandsMark Levedahl, May 14, 2026
  47. Johannes SixtMay 15, 2026
  48. Johannes SixtMay 15, 2026
  49. Johannes SixtMay 15, 2026
  50. Aina BootMay 15, 2026
  51. Mark LevedahlMay 15, 2026
  52. Johannes SixtMay 15, 2026
  53. Johannes SixtMay 15, 2026
  54. Johannes SixtMay 15, 2026
  55. Johannes SixtMay 15, 2026
  56. Johannes SixtMay 15, 2026
  57. Johannes SixtMay 15, 2026
  58. Johannes SixtMay 16, 2026
  59. Johannes SixtMay 16, 2026
  60. Johannes SixtMay 16, 2026
  61. Johannes SixtMay 16, 2026
  62. Johannes SixtMay 16, 2026
  63. Mark LevedahlMay 16, 2026
  64. Mark LevedahlMay 16, 2026
  65. Mark LevedahlMay 16, 2026
  66. Mark LevedahlMay 16, 2026
  67. Mark LevedahlMay 16, 2026
  68. Mark LevedahlMay 16, 2026
  69. Mark LevedahlMay 16, 2026
  70. Mark LevedahlMay 16, 2026
  71. Mark LevedahlMay 16, 2026
  72. Johannes SixtMay 19, 2026
  73. Johannes SixtMay 19, 2026
  74. Mark LevedahlMay 19, 2026
  75. Mark LevedahlMay 19, 2026
  76. Johannes SixtMay 19, 2026
  77. 00/11 Improve git gui operation without a worktreeMark Levedahl, May 20, 2026
  78. 01/11 git-gui: guard set/unset of GIT_DIR and GIT_WORK_TREEMark Levedahl, May 20, 2026
  79. 02/11 git-gui: return status from choose_repository::pickMark Levedahl, May 20, 2026
  80. 04/11 git-gui: use rev-parse exclusively to find a repositoryMark Levedahl, May 20, 2026
  81. 05/11 git-gui: simplify [is_bare] to report if a worktree is knownMark Levedahl, May 20, 2026
  82. 06/11 git-gui: use git rev-parse for worktree discoveryMark Levedahl, May 20, 2026
  83. 07/11 git-gui: try harder to find worktree from gitdirMark Levedahl, May 20, 2026
  84. 03/11 git-gui: use --absolute-git-dirMark Levedahl, May 20, 2026
  85. 08/11 git-gui: use HEAD as current branch when detached (bug fix)Mark Levedahl, May 20, 2026
  86. 09/11 git-gui: allow specifying path '.' to the browserMark Levedahl, May 20, 2026
  87. 10/11 git-gui: adapt blame/browser parsing for bare operationMark Levedahl, May 20, 2026
  88. 11/11 git-gui: add gui and pick as explicit subcommandsMark Levedahl, May 20, 2026
  89. Shroom MooMay 21, 2026
  90. Shroom MooMay 21, 2026
  91. Mark LevedahlMay 21, 2026
  92. Mark LevedahlMay 21, 2026
  93. Johannes SixtMay 22, 2026
  94. Johannes SixtMay 22, 2026
  95. Johannes SixtMay 22, 2026
  96. Johannes SixtMay 22, 2026
  97. Mark LevedahlMay 22, 2026
  98. Mark LevedahlMay 22, 2026
  99. Shroom MooMay 22, 2026
  100. Shroom MooMay 22, 2026
  101. Mark LevedahlMay 22, 2026
  102. Mark LevedahlMay 22, 2026
  103. Johannes SixtMay 23, 2026
  104. Johannes SixtMay 23, 2026
  105. Aina BootMay 23, 2026
  106. Shroom MooMay 23, 2026
  107. Johannes SixtMay 23, 2026
  108. Johannes SixtMay 23, 2026
  109. Johannes SixtMay 23, 2026
  110. Johannes SixtMay 23, 2026
  111. Mark LevedahlMay 23, 2026
  112. Mark LevedahlMay 23, 2026
  113. Mark LevedahlMay 23, 2026
  114. fixup git-gui: allow blame to show uncommitted changesMark Levedahl, May 23, 2026
  115. Johannes SixtMay 23, 2026
  116. Johannes SixtMay 24, 2026
  117. Johannes SixtMay 24, 2026
  118. Mark LevedahlMay 25, 2026
  119. 00/12 Improve git gui operation without a worktreeMark Levedahl, May 31, 2026
  120. 01/12 git-gui: use HEAD as current branch when detachedMark Levedahl, May 31, 2026
  121. 02/12 git-gui: remove unnecessary 'cd $_gitworktree' from do_gitkMark Levedahl, May 31, 2026
  122. 03/12 git-gui: guard set/unset of GIT_DIR and GIT_WORK_TREEMark Levedahl, May 31, 2026
  123. 04/12 git-gui: do not change global vars in choose_repository::pickMark Levedahl, May 31, 2026
  124. 05/12 git-gui: use --absolute-git-dirMark Levedahl, May 31, 2026
  125. 06/12 git-gui: use rev-parse exclusively to find a repositoryMark Levedahl, May 31, 2026
  126. 07/12 git-gui: use git rev-parse for worktree discoveryMark Levedahl, May 31, 2026
  127. 08/12 git-gui: simplify [is_bare] to report if a worktree is knownMark Levedahl, May 31, 2026
  128. 09/12 git-gui: try harder to find worktree from gitdirMark Levedahl, May 31, 2026
  129. 10/12 git-gui: allow specifying path '.' to the browserMark Levedahl, May 31, 2026
  130. 11/12 git-gui: check browser/blame arguments carefullyMark Levedahl, May 31, 2026
  131. 12/12 git-gui: add gui and pick as explicit subcommandsMark Levedahl, May 31, 2026
  132. Johannes SixtJun 2, 2026
  133. Mark LevedahlJun 2, 2026
  134. Johannes SixtJun 2, 2026

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.