git-sh-setup.sh: make GIT_EDITOR/core.editor/VISUAL/EDITOR accept commands
The previous code only allowed specifying a single executable rather than a complete command like "emacsclient --alternate-editor vi" in those variables. Since VISUAL/EDITOR appear to be traditionally passed to a shell for interpretation (as corroborated with "less", "mail" and "mailx", while the really ancient "more" indeed allows only an executable name), the shell function git_editor has been amended appropriately. "eval" is employed to have quotes and similar interpreted _after_ expansion, so that specifying EDITOR='"/home/dak/My Commands/notepad.exe"' can be used for actually using commands with blanks. Instead of passing just the first argument of git_editor on, we pass all of them (so that +lineno might be employed at a later point of time, or so that multiple files may be edited when appropriate). Strictly speaking, there is a change in behavior: when git config core.editor returns a valid but empty string, the fallbacks are still searched. This is more consistent, and the old code was problematic with regard to multiple blanks. Putting in additional quotes might have worked, but quotes inside of command substitution inside of quotes is nasty enough to not reliably work the same across "Bourne shells". Signed-off-by: David Kastrup <dak@gnu.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
21e9757e31
commit
08874658b4
@ -29,7 +29,8 @@ set_reflog_action() {
|
||||
}
|
||||
|
||||
git_editor() {
|
||||
GIT_EDITOR=${GIT_EDITOR:-$(git config core.editor || echo ${VISUAL:-${EDITOR}})}
|
||||
: "${GIT_EDITOR:=$(git config core.editor)}"
|
||||
: "${GIT_EDITOR:=${VISUAL:-${EDITOR}}}"
|
||||
case "$GIT_EDITOR,$TERM" in
|
||||
,dumb)
|
||||
echo >&2 "No editor specified in GIT_EDITOR, core.editor, VISUAL,"
|
||||
@ -40,7 +41,7 @@ git_editor() {
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
"${GIT_EDITOR:-vi}" "$1"
|
||||
eval "${GIT_EDITOR:=vi}" '"$@"'
|
||||
}
|
||||
|
||||
is_bare_repository () {
|
||||
|
Loading…
Reference in New Issue
Block a user