![]() Used to specify custom color for specified git status elements. A boolean value that enables or disables color output for Git status.Enables or disables color output for the git show branch command.A brief summary is available by running grep -help. You may also find more information about Grep by running info grep or man grep, or by looking at /usr/share/doc/grep/, /usr/local/doc/grep/, or similar directories on your system. Enables or disables colored output when the pager is in use Documentation for Grep is available online, as is documentation for most GNU software.The available values are: prompt, header, help, error and each act on the corresponding interactive output. The variable can be specified to target more specific "interactive output".Examples are git add -interactive and git clean -interactive This variable applies color for interactive prompts and displays.separator: separators between fields on a line (:, -, and =) and between hunks (-) selected: non-matching text in selected lines ![]() ![]() matchSelected: matching text in selected lines matchContext: matching text in context lines context: non-matching text in context lines The variable specifies which part of the grep output to apply color. Applies color to the output of git grep.They are respectively applicable to local branches, remote-tracking branches, tags, stashed changes and HEAD. The supported values are: branch, remoteBranch, tag, stash, or HEAD. Customize the color for git log -decorate output.whitespace: sets a color for any whitespace errors in a diff commit: colors commit headers within the diff old: applies a color to the removed lines in the diff frag: applies color to the "hunk header" or "function in hunk header" meta: applies color to the meta information of the diff Git context is the lines of text content shown in a diff or patch that highlights changes. Configuring a value under color.diff tells git which part of the patch to use a specific color on.Applies colors to git diff, git log, and git show output.remote: a remote branch ref in refs/remotes This value is also applicable to Git branch output.Configures the output color of the Git branch command.This means when looking for a configuration value, Git will start at the local level and bubble up to the system level. Thus the order of priority for configuration levels is: local, global, system. On windows this file can be found at C:\Documents and Settings\All Users\Application Data\Git\config on Windows XP, and in C:\ProgramData\Git\config on Windows Vista and newer. The system level configuration file lives in a gitconfig file off the system root path. This covers all users on an operating system and all repos. System-level configuration is applied across an entire machine. ~ /.gitconfig on unix systems and C:\Users\ \.gitconfig on windows Global configuration values are stored in a file that is located in a user's home directory. Global level configuration is user-specific, meaning it is applied to an operating system user. Local configuration values are stored in a file that can be found in the repo's. Local level configuration is applied to the context repository git config gets invoked in. By default, git config will write to a local level if no configuration option is passed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |