2012-11-28 18:26:43 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='basic sanity checks for git var'
|
2021-10-12 13:56:37 +00:00
|
|
|
|
|
|
|
TEST_PASSES_SANITIZE_LEAK=true
|
2012-11-28 18:26:43 +00:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
2022-11-26 14:17:57 +00:00
|
|
|
sane_unset_all_editors () {
|
|
|
|
sane_unset GIT_EDITOR &&
|
|
|
|
sane_unset VISUAL &&
|
|
|
|
sane_unset EDITOR
|
|
|
|
}
|
|
|
|
|
2012-11-28 18:26:43 +00:00
|
|
|
test_expect_success 'get GIT_AUTHOR_IDENT' '
|
|
|
|
test_tick &&
|
|
|
|
echo "$GIT_AUTHOR_NAME <$GIT_AUTHOR_EMAIL> $GIT_AUTHOR_DATE" >expect &&
|
|
|
|
git var GIT_AUTHOR_IDENT >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_COMMITTER_IDENT' '
|
|
|
|
test_tick &&
|
|
|
|
echo "$GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> $GIT_COMMITTER_DATE" >expect &&
|
|
|
|
git var GIT_COMMITTER_IDENT >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
'
|
|
|
|
|
2020-04-04 14:16:21 +00:00
|
|
|
test_expect_success !FAIL_PREREQS,!AUTOIDENT 'requested identities are strict' '
|
2012-11-28 18:26:43 +00:00
|
|
|
(
|
|
|
|
sane_unset GIT_COMMITTER_NAME &&
|
|
|
|
sane_unset GIT_COMMITTER_EMAIL &&
|
|
|
|
test_must_fail git var GIT_COMMITTER_IDENT
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2021-11-03 20:17:02 +00:00
|
|
|
test_expect_success 'get GIT_DEFAULT_BRANCH without configuration' '
|
|
|
|
(
|
|
|
|
sane_unset GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME &&
|
|
|
|
git init defbranch &&
|
|
|
|
git -C defbranch symbolic-ref --short HEAD >expect &&
|
|
|
|
git var GIT_DEFAULT_BRANCH >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_DEFAULT_BRANCH with configuration' '
|
|
|
|
test_config init.defaultbranch foo &&
|
|
|
|
(
|
|
|
|
sane_unset GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME &&
|
|
|
|
echo foo >expect &&
|
|
|
|
git var GIT_DEFAULT_BRANCH >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2022-11-26 14:17:57 +00:00
|
|
|
test_expect_success 'get GIT_EDITOR without configuration' '
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
test_expect_code 1 git var GIT_EDITOR >out &&
|
|
|
|
test_must_be_empty out
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_EDITOR with configuration' '
|
|
|
|
test_config core.editor foo &&
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
echo foo >expect &&
|
|
|
|
git var GIT_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_EDITOR with environment variable GIT_EDITOR' '
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
echo bar >expect &&
|
|
|
|
GIT_EDITOR=bar git var GIT_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_EDITOR with environment variable EDITOR' '
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
echo bar >expect &&
|
|
|
|
EDITOR=bar git var GIT_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_EDITOR with configuration and environment variable GIT_EDITOR' '
|
|
|
|
test_config core.editor foo &&
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
echo bar >expect &&
|
|
|
|
GIT_EDITOR=bar git var GIT_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_EDITOR with configuration and environment variable EDITOR' '
|
|
|
|
test_config core.editor foo &&
|
|
|
|
(
|
|
|
|
sane_unset_all_editors &&
|
|
|
|
echo foo >expect &&
|
|
|
|
EDITOR=bar git var GIT_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2022-12-17 23:09:59 +00:00
|
|
|
test_expect_success 'get GIT_SEQUENCE_EDITOR without configuration' '
|
|
|
|
(
|
|
|
|
sane_unset GIT_SEQUENCE_EDITOR &&
|
|
|
|
git var GIT_EDITOR >expect &&
|
|
|
|
git var GIT_SEQUENCE_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_SEQUENCE_EDITOR with configuration' '
|
|
|
|
test_config sequence.editor foo &&
|
|
|
|
(
|
|
|
|
sane_unset GIT_SEQUENCE_EDITOR &&
|
|
|
|
echo foo >expect &&
|
|
|
|
git var GIT_SEQUENCE_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_SEQUENCE_EDITOR with environment variable' '
|
|
|
|
(
|
|
|
|
sane_unset GIT_SEQUENCE_EDITOR &&
|
|
|
|
echo bar >expect &&
|
|
|
|
GIT_SEQUENCE_EDITOR=bar git var GIT_SEQUENCE_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'get GIT_SEQUENCE_EDITOR with configuration and environment variable' '
|
|
|
|
test_config sequence.editor foo &&
|
|
|
|
(
|
|
|
|
sane_unset GIT_SEQUENCE_EDITOR &&
|
|
|
|
echo bar >expect &&
|
|
|
|
GIT_SEQUENCE_EDITOR=bar git var GIT_SEQUENCE_EDITOR >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
var: add support for listing the shell
On most Unix systems, finding a suitable shell is easy: one simply uses
"sh" with an appropriate PATH value. However, in many Windows
environments, the shell is shipped alongside Git, and it may or may not
be in PATH, even if Git is.
In such an environment, it can be very helpful to query Git for the
shell it's using, since other tools may want to use the same shell as
well. To help them out, let's add a variable, GIT_SHELL_PATH, that
points to the location of the shell.
On Unix, we know our shell must be executable to be functional, so
assume that the distributor has correctly configured their environment,
and use that as a basic test. On Git for Windows, we know that our
shell will be one of a few fixed values, all of which end in "sh" (such
as "bash"). This seems like it might be a nice test on Unix as well,
since it is customary for all shells to end in "sh", but there probably
exist such systems that don't have such a configuration, so be careful
here not to break them.
Signed-off-by: brian m. carlson <bk2204@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-27 16:18:57 +00:00
|
|
|
test_expect_success POSIXPERM 'GIT_SHELL_PATH points to a valid executable' '
|
|
|
|
shellpath=$(git var GIT_SHELL_PATH) &&
|
|
|
|
test_path_is_executable "$shellpath"
|
|
|
|
'
|
|
|
|
|
|
|
|
# We know in this environment that our shell will be one of a few fixed values
|
|
|
|
# that all end in "sh".
|
|
|
|
test_expect_success MINGW 'GIT_SHELL_PATH points to a suitable shell' '
|
|
|
|
shellpath=$(git var GIT_SHELL_PATH) &&
|
|
|
|
case "$shellpath" in
|
var(win32): do report the GIT_SHELL_PATH that is actually used
On Windows, Unix-like paths like `/bin/sh` make very little sense. In
the best case, they simply don't work, in the worst case they are
misinterpreted as absolute paths that are relative to the drive
associated with the current directory.
To that end, Git does not actually use the path `/bin/sh` that is
recorded e.g. when `run_command()` is called with a Unix shell
command-line. Instead, as of 776297548e (Do not use SHELL_PATH from
build system in prepare_shell_cmd on Windows, 2012-04-17), it
re-interprets `/bin/sh` as "look up `sh` on the `PATH` and use the
result instead".
This is the logic users expect to be followed when running `git var
GIT_SHELL_PATH`.
However, when 1e65721227 (var: add support for listing the shell,
2023-06-27) introduced support for `git var GIT_SHELL_PATH`, Windows was
not special-cased as above, which is why it outputs `/bin/sh` even
though that disagrees with what Git actually uses.
Let's fix this by using the exact same logic as `prepare_shell_cmd()`,
adjusting the Windows-specific `git var GIT_SHELL_PATH` test case to
verify that it actually finds a working executable.
Reported-by: Phillip Wood <phillip.wood123@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2024-07-13 21:08:24 +00:00
|
|
|
[A-Z]:/*/sh.exe) test -f "$shellpath";;
|
var: add support for listing the shell
On most Unix systems, finding a suitable shell is easy: one simply uses
"sh" with an appropriate PATH value. However, in many Windows
environments, the shell is shipped alongside Git, and it may or may not
be in PATH, even if Git is.
In such an environment, it can be very helpful to query Git for the
shell it's using, since other tools may want to use the same shell as
well. To help them out, let's add a variable, GIT_SHELL_PATH, that
points to the location of the shell.
On Unix, we know our shell must be executable to be functional, so
assume that the distributor has correctly configured their environment,
and use that as a basic test. On Git for Windows, we know that our
shell will be one of a few fixed values, all of which end in "sh" (such
as "bash"). This seems like it might be a nice test on Unix as well,
since it is customary for all shells to end in "sh", but there probably
exist such systems that don't have such a configuration, so be careful
here not to break them.
Signed-off-by: brian m. carlson <bk2204@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-27 16:18:57 +00:00
|
|
|
*) return 1;;
|
|
|
|
esac
|
|
|
|
'
|
|
|
|
|
2023-06-27 16:19:01 +00:00
|
|
|
test_expect_success 'GIT_ATTR_SYSTEM produces expected output' '
|
|
|
|
test_must_fail env GIT_ATTR_NOSYSTEM=1 git var GIT_ATTR_SYSTEM &&
|
|
|
|
(
|
|
|
|
sane_unset GIT_ATTR_NOSYSTEM &&
|
|
|
|
systempath=$(git var GIT_ATTR_SYSTEM) &&
|
|
|
|
test "$systempath" != ""
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'GIT_ATTR_GLOBAL points to the correct location' '
|
|
|
|
TRASHDIR="$(test-tool path-utils normalize_path_copy "$(pwd)")" &&
|
|
|
|
globalpath=$(XDG_CONFIG_HOME="$TRASHDIR/.config" git var GIT_ATTR_GLOBAL) &&
|
|
|
|
test "$globalpath" = "$TRASHDIR/.config/git/attributes" &&
|
|
|
|
(
|
|
|
|
sane_unset XDG_CONFIG_HOME &&
|
|
|
|
globalpath=$(HOME="$TRASHDIR" git var GIT_ATTR_GLOBAL) &&
|
|
|
|
test "$globalpath" = "$TRASHDIR/.config/git/attributes"
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
var: add config file locations
Much like with attributes files, sometimes programs would like to know
the location of configuration files at the global or system levels.
However, it isn't always clear where these may live, especially for the
system file, which may have been hard-coded at compile time or computed
dynamically based on the runtime prefix.
Since other parties cannot intuitively know how Git was compiled and
where it looks for these files, help them by providing variables that
can be queried. Because we have multiple paths for global config
values, print them in order from highest to lowest priority, and be sure
to split on newlines so that "git var -l" produces two entries for the
global value.
However, be careful not to split all values on newlines, since our
editor values could well contain such characters, and we don't want to
split them in such a case.
Note in the documentation that some values may contain multiple paths
and that callers should be prepared for that fact. This helps people
write code that will continue to work in the event we allow multiple
items elsewhere in the future.
Signed-off-by: brian m. carlson <bk2204@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-27 16:19:02 +00:00
|
|
|
test_expect_success 'GIT_CONFIG_SYSTEM points to the correct location' '
|
|
|
|
TRASHDIR="$(test-tool path-utils normalize_path_copy "$(pwd)")" &&
|
|
|
|
test_must_fail env GIT_CONFIG_NOSYSTEM=1 git var GIT_CONFIG_SYSTEM &&
|
|
|
|
(
|
|
|
|
sane_unset GIT_CONFIG_NOSYSTEM &&
|
|
|
|
systempath=$(git var GIT_CONFIG_SYSTEM) &&
|
|
|
|
test "$systempath" != "" &&
|
|
|
|
systempath=$(GIT_CONFIG_SYSTEM=/dev/null git var GIT_CONFIG_SYSTEM) &&
|
|
|
|
if test_have_prereq MINGW
|
|
|
|
then
|
|
|
|
test "$systempath" = "nul"
|
|
|
|
else
|
|
|
|
test "$systempath" = "/dev/null"
|
|
|
|
fi &&
|
|
|
|
systempath=$(GIT_CONFIG_SYSTEM="$TRASHDIR/gitconfig" git var GIT_CONFIG_SYSTEM) &&
|
|
|
|
test "$systempath" = "$TRASHDIR/gitconfig"
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'GIT_CONFIG_GLOBAL points to the correct location' '
|
|
|
|
TRASHDIR="$(test-tool path-utils normalize_path_copy "$(pwd)")" &&
|
|
|
|
HOME="$TRASHDIR" XDG_CONFIG_HOME="$TRASHDIR/foo" git var GIT_CONFIG_GLOBAL >actual &&
|
|
|
|
echo "$TRASHDIR/foo/git/config" >expected &&
|
|
|
|
echo "$TRASHDIR/.gitconfig" >>expected &&
|
|
|
|
test_cmp expected actual &&
|
|
|
|
(
|
|
|
|
sane_unset XDG_CONFIG_HOME &&
|
|
|
|
HOME="$TRASHDIR" git var GIT_CONFIG_GLOBAL >actual &&
|
|
|
|
echo "$TRASHDIR/.config/git/config" >expected &&
|
|
|
|
echo "$TRASHDIR/.gitconfig" >>expected &&
|
|
|
|
test_cmp expected actual &&
|
|
|
|
globalpath=$(GIT_CONFIG_GLOBAL=/dev/null git var GIT_CONFIG_GLOBAL) &&
|
|
|
|
if test_have_prereq MINGW
|
|
|
|
then
|
|
|
|
test "$globalpath" = "nul"
|
|
|
|
else
|
|
|
|
test "$globalpath" = "/dev/null"
|
|
|
|
fi &&
|
|
|
|
globalpath=$(GIT_CONFIG_GLOBAL="$TRASHDIR/gitconfig" git var GIT_CONFIG_GLOBAL) &&
|
|
|
|
test "$globalpath" = "$TRASHDIR/gitconfig"
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2012-11-28 18:26:43 +00:00
|
|
|
# For git var -l, we check only a representative variable;
|
|
|
|
# testing the whole output would make our test too brittle with
|
|
|
|
# respect to unrelated changes in the test suite's environment.
|
|
|
|
test_expect_success 'git var -l lists variables' '
|
|
|
|
git var -l >actual &&
|
|
|
|
echo "$GIT_AUTHOR_NAME <$GIT_AUTHOR_EMAIL> $GIT_AUTHOR_DATE" >expect &&
|
|
|
|
sed -n s/GIT_AUTHOR_IDENT=//p <actual >actual.author &&
|
|
|
|
test_cmp expect actual.author
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'git var -l lists config' '
|
|
|
|
git var -l >actual &&
|
|
|
|
echo false >expect &&
|
|
|
|
sed -n s/core\\.bare=//p <actual >actual.bare &&
|
|
|
|
test_cmp expect actual.bare
|
|
|
|
'
|
|
|
|
|
var: add config file locations
Much like with attributes files, sometimes programs would like to know
the location of configuration files at the global or system levels.
However, it isn't always clear where these may live, especially for the
system file, which may have been hard-coded at compile time or computed
dynamically based on the runtime prefix.
Since other parties cannot intuitively know how Git was compiled and
where it looks for these files, help them by providing variables that
can be queried. Because we have multiple paths for global config
values, print them in order from highest to lowest priority, and be sure
to split on newlines so that "git var -l" produces two entries for the
global value.
However, be careful not to split all values on newlines, since our
editor values could well contain such characters, and we don't want to
split them in such a case.
Note in the documentation that some values may contain multiple paths
and that callers should be prepared for that fact. This helps people
write code that will continue to work in the event we allow multiple
items elsewhere in the future.
Signed-off-by: brian m. carlson <bk2204@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-27 16:19:02 +00:00
|
|
|
test_expect_success 'git var -l lists multiple global configs' '
|
|
|
|
TRASHDIR="$(test-tool path-utils normalize_path_copy "$(pwd)")" &&
|
|
|
|
HOME="$TRASHDIR" XDG_CONFIG_HOME="$TRASHDIR/foo" git var -l >actual &&
|
|
|
|
grep "^GIT_CONFIG_GLOBAL=" actual >filtered &&
|
|
|
|
echo "GIT_CONFIG_GLOBAL=$TRASHDIR/foo/git/config" >expected &&
|
|
|
|
echo "GIT_CONFIG_GLOBAL=$TRASHDIR/.gitconfig" >>expected &&
|
|
|
|
test_cmp expected filtered
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'git var -l does not split multiline editors' '
|
|
|
|
(
|
|
|
|
GIT_EDITOR="!f() {
|
|
|
|
echo Hello!
|
|
|
|
}; f" &&
|
|
|
|
export GIT_EDITOR &&
|
|
|
|
echo "GIT_EDITOR=$GIT_EDITOR" >expected &&
|
|
|
|
git var -l >var &&
|
|
|
|
sed -n -e "/^GIT_EDITOR/,\$p" var | head -n 3 >actual &&
|
|
|
|
test_cmp expected actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2012-11-28 18:26:43 +00:00
|
|
|
test_expect_success 'listing and asking for variables are exclusive' '
|
|
|
|
test_must_fail git var -l GIT_COMMITTER_IDENT
|
|
|
|
'
|
|
|
|
|
2023-09-04 06:21:26 +00:00
|
|
|
test_expect_success '`git var -l` works even without HOME' '
|
|
|
|
(
|
|
|
|
XDG_CONFIG_HOME= &&
|
|
|
|
export XDG_CONFIG_HOME &&
|
|
|
|
unset HOME &&
|
|
|
|
git var -l
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2012-11-28 18:26:43 +00:00
|
|
|
test_done
|