2005-07-15 00:55:09 +00:00
|
|
|
git-var(1)
|
2005-07-15 21:57:09 +00:00
|
|
|
==========
|
2005-07-15 00:55:09 +00:00
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2013-01-21 19:17:53 +00:00
|
|
|
git-var - Show a Git logical variable
|
2005-07-15 00:55:09 +00:00
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2011-07-02 02:38:26 +00:00
|
|
|
[verse]
|
2022-10-13 15:39:06 +00:00
|
|
|
'git var' (-l | <variable>)
|
2005-07-15 00:55:09 +00:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2022-11-26 14:17:56 +00:00
|
|
|
Prints a Git logical variable. Exits with code 1 if the variable has
|
|
|
|
no value.
|
2005-07-15 00:55:09 +00:00
|
|
|
|
2005-10-03 17:16:30 +00:00
|
|
|
OPTIONS
|
|
|
|
-------
|
|
|
|
-l::
|
2006-04-24 22:59:28 +00:00
|
|
|
Cause the logical variables to be listed. In addition, all the
|
2013-01-21 19:17:53 +00:00
|
|
|
variables of the Git configuration file .git/config are listed
|
2006-04-24 22:59:30 +00:00
|
|
|
as well. (However, the configuration variables listing functionality
|
2010-01-07 16:49:12 +00:00
|
|
|
is deprecated in favor of `git config -l`.)
|
2005-07-15 00:55:09 +00:00
|
|
|
|
2018-04-30 15:35:33 +00:00
|
|
|
EXAMPLES
|
2005-07-15 00:55:09 +00:00
|
|
|
--------
|
2008-06-30 06:09:04 +00:00
|
|
|
$ git var GIT_AUTHOR_IDENT
|
2005-10-03 17:16:30 +00:00
|
|
|
Eric W. Biederman <ebiederm@lnxi.com> 1121223278 -0600
|
2005-07-15 00:55:09 +00:00
|
|
|
|
|
|
|
|
|
|
|
VARIABLES
|
2018-04-30 15:35:33 +00:00
|
|
|
---------
|
2005-10-03 17:16:30 +00:00
|
|
|
GIT_AUTHOR_IDENT::
|
2005-07-15 00:55:09 +00:00
|
|
|
The author of a piece of code.
|
|
|
|
|
2005-10-03 17:16:30 +00:00
|
|
|
GIT_COMMITTER_IDENT::
|
2013-01-21 19:17:53 +00:00
|
|
|
The person who put a piece of code into Git.
|
2005-07-15 00:55:09 +00:00
|
|
|
|
2009-11-12 00:01:27 +00:00
|
|
|
GIT_EDITOR::
|
2013-01-21 19:17:53 +00:00
|
|
|
Text editor for use by Git commands. The value is meant to be
|
2009-11-12 00:01:27 +00:00
|
|
|
interpreted by the shell when it is used. Examples: `~/bin/vi`,
|
|
|
|
`$SOME_ENVIRONMENT_VARIABLE`, `"C:\Program Files\Vim\gvim.exe"
|
|
|
|
--nofork`. The order of preference is the `$GIT_EDITOR`
|
|
|
|
environment variable, then `core.editor` configuration, then
|
2012-03-31 08:42:34 +00:00
|
|
|
`$VISUAL`, then `$EDITOR`, and then the default chosen at compile
|
|
|
|
time, which is usually 'vi'.
|
2012-03-31 08:44:53 +00:00
|
|
|
ifdef::git-default-editor[]
|
|
|
|
The build you are using chose '{git-default-editor}' as the default.
|
|
|
|
endif::git-default-editor[]
|
2009-11-12 00:01:27 +00:00
|
|
|
|
2022-12-17 23:09:59 +00:00
|
|
|
GIT_SEQUENCE_EDITOR::
|
|
|
|
Text editor used to edit the 'todo' file while running `git rebase
|
|
|
|
-i`. Like `GIT_EDITOR`, the value is meant to be interpreted by
|
|
|
|
the shell when it is used. The order of preference is the
|
|
|
|
`$GIT_SEQUENCE_EDITOR` environment variable, then
|
|
|
|
`sequence.editor` configuration, and then the value of `git var
|
|
|
|
GIT_EDITOR`.
|
|
|
|
|
2009-10-31 01:41:27 +00:00
|
|
|
GIT_PAGER::
|
2013-01-21 19:17:53 +00:00
|
|
|
Text viewer for use by Git commands (e.g., 'less'). The value
|
2009-10-31 01:41:27 +00:00
|
|
|
is meant to be interpreted by the shell. The order of preference
|
|
|
|
is the `$GIT_PAGER` environment variable, then `core.pager`
|
2012-03-31 08:42:34 +00:00
|
|
|
configuration, then `$PAGER`, and then the default chosen at
|
|
|
|
compile time (usually 'less').
|
2012-03-31 08:44:53 +00:00
|
|
|
ifdef::git-default-pager[]
|
|
|
|
The build you are using chose '{git-default-pager}' as the default.
|
|
|
|
endif::git-default-pager[]
|
2009-10-31 01:41:27 +00:00
|
|
|
|
2021-11-03 20:17:02 +00:00
|
|
|
GIT_DEFAULT_BRANCH::
|
|
|
|
The name of the first branch created in newly initialized repositories.
|
|
|
|
|
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
|
|
|
GIT_SHELL_PATH::
|
|
|
|
The path of the binary providing the POSIX shell for commands which use the shell.
|
|
|
|
|
2008-05-28 23:55:27 +00:00
|
|
|
SEE ALSO
|
2005-07-15 00:55:09 +00:00
|
|
|
--------
|
2007-12-29 06:20:38 +00:00
|
|
|
linkgit:git-commit-tree[1]
|
|
|
|
linkgit:git-tag[1]
|
|
|
|
linkgit:git-config[1]
|
2005-07-15 00:55:09 +00:00
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 07:07:32 +00:00
|
|
|
Part of the linkgit:git[1] suite
|