0f6f5a4022
This adds an option to help scripts find out color settings from
the configuration file.
git config --get-colorbool color.diff
inspects color.diff variable, and exits with status 0 (i.e. success) if
color is to be used. It exits with status 1 otherwise.
If a script wants "true"/"false" answer to the standard output of the
command, it can pass an additional boolean parameter to its command
line, telling if its standard output is a terminal, like this:
git config --get-colorbool color.diff true
When called like this, the command outputs "true" to its standard output
if color is to be used (i.e. "color.diff" says "always", "auto", or
"true"), and "false" otherwise.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
13 lines
417 B
C
13 lines
417 B
C
#ifndef COLOR_H
|
|
#define COLOR_H
|
|
|
|
/* "\033[1;38;5;2xx;48;5;2xxm\0" is 23 bytes */
|
|
#define COLOR_MAXLEN 24
|
|
|
|
int git_config_colorbool(const char *var, const char *value, int stdout_is_tty);
|
|
void color_parse(const char *var, const char *value, char *dst);
|
|
int color_fprintf(FILE *fp, const char *color, const char *fmt, ...);
|
|
int color_fprintf_ln(FILE *fp, const char *color, const char *fmt, ...);
|
|
|
|
#endif /* COLOR_H */
|