diff options
author | Chayoung You <yousbe@gmail.com> | 2019-01-01 23:05:08 +0900 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-01-03 11:48:13 -0800 |
commit | 7a478b36aa1f202aed207a230def66563227f30e (patch) | |
tree | 4f583d079a138172f12f3bcd31acd35f01b12418 /builtin/rerere.c | |
parent | Sync with Git 2.20.1 (diff) | |
download | tgif-7a478b36aa1f202aed207a230def66563227f30e.tar.xz |
zsh: complete unquoted paths with spaces correctly
The following is the description of -Q flag of zsh compadd [1]:
This flag instructs the completion code not to quote any
metacharacters in the words when inserting them into the command
line.
Let's say there is a file named 'foo bar.txt' in repository, but it's
not yet added to the repository. Then the following command triggers a
completion:
git add fo<Tab>
git add 'fo<Tab>
git add "fo<Tab>
The completion results in bash:
git add foo\ bar.txt
git add 'foo bar.txt'
git add "foo bar.txt"
While them in zsh:
git add foo bar.txt
git add 'foo bar.txt'
git add "foo bar.txt"
The first one, where the pathname is not enclosed in quotes, should
escape the space with a backslash, just like bash completion does.
Otherwise, this leads git to think there are two files; foo, and
bar.txt.
The main cause of this behavior is __gitcomp_file_direct(). The both
implementions of bash and zsh are called with an argument 'foo bar.txt',
but only bash adds a backslash before a space on command line.
[1]: http://zsh.sourceforge.net/Doc/Release/Completion-Widgets.html
Signed-off-by: Chayoung You <yousbe@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/rerere.c')
0 files changed, 0 insertions, 0 deletions