summaryrefslogtreecommitdiff
path: root/cache-tree.h
diff options
context:
space:
mode:
authorSardorbek Imomaliev <sardorbek.imomaliev@gmail.com>2021-05-03 16:29:07 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-05-04 03:17:23 (GMT)
commitf2acf763e29a3696fef268a9e8dc421e807df7f2 (patch)
treea4266b5e611573da0e75fd89a1af5ac600a5f2b3 /cache-tree.h
parent48bf2fa8bad054d66bd79c6ba903c89c704201f7 (diff)
downloadgit-f2acf763e29a3696fef268a9e8dc421e807df7f2.zip
git-f2acf763e29a3696fef268a9e8dc421e807df7f2.tar.gz
git-f2acf763e29a3696fef268a9e8dc421e807df7f2.tar.bz2
work around zsh comment in __git_complete_worktree_paths
[PATCH]: contrib/completion/git-completion.bash, there is a construct where comment lines are placed between the command that is on the upstream of a pipe and the command that is on the downstream of a pipe in __git_complete_worktree_paths function. Unfortunately, this script is also used by Zsh completion, but Zsh mishandles this construct when "interactive_comments" option is not set (by default it is off on macOS), resulting in a breakage: $ git worktree remove [TAB] $ git worktree remove __git_complete_worktree_paths:7: command not found: # Move the comment, even though it explains what happens on the downstream of the pipe and logically belongs where it is right now, before the entire pipeline, to work around this problem. Signed-off-by: Sardorbek Imomaliev <sardorbek.imomaliev@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'cache-tree.h')
0 files changed, 0 insertions, 0 deletions