aboutsummaryrefslogtreecommitdiff
path: root/t/t0021-conversion.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <Johannes.Schindelin@gmx.de>2008-03-11 10:56:30 +0100
committerJunio C Hamano <gitster@pobox.com>2008-03-11 19:57:56 -0700
commitfc99469a2b786676ffe48d5966d71cea3613b716 (patch)
tree028afe90d4f8331a37f82b42169cbefd98f2ec9b /t/t0021-conversion.sh
parent4201bb5f7e408143dc5bf35497cc82bc803fe9fb (diff)
downloadgit-fc99469a2b786676ffe48d5966d71cea3613b716.tar.gz
git-fc99469a2b786676ffe48d5966d71cea3613b716.tar.xz
launch_editor(): allow spaces in the filename
The construct sh -c "$0 \"$@\"" <editor> <file> does not pick up quotes in <editor>, so you cannot give path to the editor that has a shell IFS whitespace in it, and also give it initial set of parameters and flags. Replace $0 with <editor> to fix this issue. This fixes git config core.editor '"c:/Program Files/What/Ever.exe"' In other words, you can specify an editor with spaces in its path using a config containing something like this: [core] editor = \"c:/Program Files/Darn/Spaces.exe\" NOTE: we cannot just replace the $0 with \"$0\", because we still want this to work: [core] editor = emacs -nw Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t0021-conversion.sh')
0 files changed, 0 insertions, 0 deletions