# git-var(1) Manual Page

## NAME

git-var - Show a Git logical variable

## SYNOPSIS

    git var (-l | <variable>)

## DESCRIPTION

Prints a Git logical variable. Exits with code 1 if the variable has no value.

## OPTIONS

  Display the logical variables. In addition, all the variables of the Git configuration file .git/config are listed as well. (However, the configuration variables listing functionality is deprecated in favor of .)

## EXAMPLES

    $ git var GIT_AUTHOR_IDENT
    Eric W. Biederman <ebiederm@lnxi.com> 1121223278 -0600

## VARIABLES

  The author of a piece of code.

  The person who put a piece of code into Git.

  Text editor for use by Git commands. The value is meant to be interpreted by the shell when it is used. Examples: , , . The order of preference is , then configuration value, then , then , and then the default chosen at compile time, which is usually vi.

  Text editor used to edit the todo file while running . Like , the value is meant to be interpreted by the shell when it is used. The order of preference is , then configuration value, and then the value of .

  Text viewer for use by Git commands (e.g., less). The value is meant to be interpreted by the shell. The order of preference is , then the value of configuration, then , and then the default chosen at compile time (usually ).

  The name of the first branch created in newly initialized repositories.

  The path of the binary providing the POSIX shell for commands which use the shell.

  The path to the system gitattributes(5) file, if one is enabled.

  The path to the global (per-user) gitattributes(5) file.

  The path to the system configuration file, if one is enabled.

  The path to the global (per-user) configuration files, if any.

Most path values contain only one value. However, some can contain multiple values, which are separated by newlines, and are listed in order from highest to lowest priority. Callers should be prepared for any such path value to contain multiple items.

Note that paths are printed even if they do not exist, but not if they are disabled by other environment variables.

## SEE ALSO

git-commit-tree(1) git-tag(1) git-config(1)

## GIT

Part of the git(1) suite