2007-10-15 07:35:37 +08:00
# ifndef PARSE_OPTIONS_H
# define PARSE_OPTIONS_H
2019-11-18 05:04:54 +08:00
/**
* Refer to Documentation / technical / api - parse - options . txt for the API doc .
*/
2007-10-15 07:35:37 +08:00
enum parse_opt_type {
2007-11-07 18:20:27 +08:00
/* special types */
2007-10-15 07:35:37 +08:00
OPTION_END ,
2007-10-15 07:38:30 +08:00
OPTION_GROUP ,
2009-05-08 03:45:08 +08:00
OPTION_NUMBER ,
2019-04-29 18:05:25 +08:00
OPTION_ALIAS ,
2007-11-07 18:20:27 +08:00
/* options with no arguments */
OPTION_BIT ,
2009-05-08 03:44:17 +08:00
OPTION_NEGBIT ,
2019-01-27 08:35:25 +08:00
OPTION_BITOP ,
parse-options: deprecate OPT_BOOLEAN
It is natural to expect that an option defined with OPT_BOOLEAN() could be
used in this way:
int option = -1; /* unspecified */
struct option options[] = {
OPT_BOOLEAN(0, "option", &option, "set option"),
OPT_END()
};
parse_options(ac, av, prefix, options, usage, 0);
if (option < 0)
... do the default thing ...
else if (!option)
... --no-option was given ...
else
... --option was given ...
to easily tell three cases apart:
- There is no mention of the `--option` on the command line;
- The variable is positively set with `--option`; or
- The variable is explicitly negated with `--no-option`.
Unfortunately, this is not the case. OPT_BOOLEAN() increments the variable
every time `--option` is given, and resets it to zero when `--no-option`
is given.
As a first step to remedy this, introduce a true boolean OPT_BOOL(), and
rename OPT_BOOLEAN() to OPT_COUNTUP(). To help transitioning, OPT_BOOLEAN
and OPTION_BOOLEAN are defined as deprecated synonyms to OPT_COUNTUP and
OPTION_COUNTUP respectively.
This is what db7244b (parse-options new features., 2007-11-07) from four
years ago started by marking OPTION_BOOLEAN as "INCR would have been a
better name".
Some existing users do depend on the count-up semantics; for example,
users of OPT__VERBOSE() could use it to raise the verbosity level with
repeated use of `-v` on the command line, but they probably should be
rewritten to use OPT__VERBOSITY() instead these days. I suspect that some
users of OPT__FORCE() may also use it to implement different level of
forcibleness but I didn't check.
On top of this patch, here are the remaining clean-up tasks that other
people can help:
- Look at each hit in "git grep -e OPT_BOOLEAN"; trace all uses of the
value that is set to the underlying variable, and if it can proven that
the variable is only used as a boolean, replace it with OPT_BOOL(). If
the caller does depend on the count-up semantics, replace it with
OPT_COUNTUP() instead.
- Same for OPTION_BOOLEAN; replace it with OPTION_SET_INT and arrange to
set 1 to the variable for a true boolean, and otherwise replace it with
OPTION_COUNTUP.
- Look at each hit in "git grep -e OPT__VERBOSE -e OPT__QUIET" and see if
they can be replaced with OPT__VERBOSITY().
I'll follow this message up with a separate patch as an example.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-09-28 07:56:49 +08:00
OPTION_COUNTUP ,
2007-11-07 18:20:27 +08:00
OPTION_SET_INT ,
/* options with arguments (usually) */
2007-10-15 07:35:37 +08:00
OPTION_STRING ,
OPTION_INTEGER ,
2015-06-22 02:25:44 +08:00
OPTION_MAGNITUDE ,
2007-10-15 07:45:45 +08:00
OPTION_CALLBACK ,
parse-options: allow git commands to invent new option types
parse-options provides a variety of option behaviors, including
OPTION_CALLBACK, which should take care of just about any sane
behavior. All supported behaviors obey the following constraint:
A --foo option can only accept (and base its behavior on)
one argument, which would be the following command-line
argument in the "unsticked" form.
Alas, some existing git commands have options that do not obey that
constraint. For example, update-index --cacheinfo takes three
arguments, and update-index --resolve takes all later parameters as
arguments.
Introduces an OPTION_LOWLEVEL_CALLBACK backdoor to parse-options so
such option types can be supported without tempting inventors of other
commands through mention in the public API. Commands can set the
callback field to a function accepting three arguments: the option
parsing context, the option itself, and a flag indicating whether the
the option was negated. When the option is encountered, that function
is called to take over from get_value(). The return value should be
zero for success, -1 for usage errors.
Thanks to Stephen Boyd for API guidance.
Improved-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-12-02 07:32:16 +08:00
OPTION_LOWLEVEL_CALLBACK ,
2009-05-24 02:53:13 +08:00
OPTION_FILENAME
2007-10-15 07:35:37 +08:00
} ;
enum parse_opt_flags {
2021-03-22 00:58:35 +08:00
PARSE_OPT_KEEP_DASHDASH = 1 < < 0 ,
PARSE_OPT_STOP_AT_NON_OPTION = 1 < < 1 ,
PARSE_OPT_KEEP_ARGV0 = 1 < < 2 ,
PARSE_OPT_KEEP_UNKNOWN = 1 < < 3 ,
PARSE_OPT_NO_INTERNAL_HELP = 1 < < 4 ,
PARSE_OPT_ONE_SHOT = 1 < < 5 ,
2021-09-28 21:14:22 +08:00
PARSE_OPT_SHELL_EVAL = 1 < < 6 ,
2007-10-15 07:35:37 +08:00
} ;
2007-10-15 07:45:45 +08:00
enum parse_opt_option_flags {
2021-03-22 00:58:35 +08:00
PARSE_OPT_OPTARG = 1 < < 0 ,
PARSE_OPT_NOARG = 1 < < 1 ,
PARSE_OPT_NONEG = 1 < < 2 ,
PARSE_OPT_HIDDEN = 1 < < 3 ,
PARSE_OPT_LASTARG_DEFAULT = 1 < < 4 ,
PARSE_OPT_NODASH = 1 < < 5 ,
PARSE_OPT_LITERAL_ARGHELP = 1 < < 6 ,
2021-03-22 00:58:36 +08:00
PARSE_OPT_FROM_ALIAS = 1 < < 7 ,
2021-03-22 00:58:35 +08:00
PARSE_OPT_NOCOMPLETE = 1 < < 9 ,
PARSE_OPT_COMP_ARG = 1 < < 10 ,
PARSE_OPT_CMDMODE = 1 < < 11 ,
2007-10-15 07:45:45 +08:00
} ;
2019-08-21 02:49:07 +08:00
enum parse_opt_result {
PARSE_OPT_COMPLETE = - 3 ,
PARSE_OPT_HELP = - 2 ,
PARSE_OPT_ERROR = - 1 , /* must be the same as error() */
PARSE_OPT_DONE = 0 , /* fixed so that "return 0" works */
PARSE_OPT_NON_OPTION ,
PARSE_OPT_UNKNOWN
} ;
2007-10-15 07:45:45 +08:00
struct option ;
typedef int parse_opt_cb ( const struct option * , const char * arg , int unset ) ;
parse-options: allow git commands to invent new option types
parse-options provides a variety of option behaviors, including
OPTION_CALLBACK, which should take care of just about any sane
behavior. All supported behaviors obey the following constraint:
A --foo option can only accept (and base its behavior on)
one argument, which would be the following command-line
argument in the "unsticked" form.
Alas, some existing git commands have options that do not obey that
constraint. For example, update-index --cacheinfo takes three
arguments, and update-index --resolve takes all later parameters as
arguments.
Introduces an OPTION_LOWLEVEL_CALLBACK backdoor to parse-options so
such option types can be supported without tempting inventors of other
commands through mention in the public API. Commands can set the
callback field to a function accepting three arguments: the option
parsing context, the option itself, and a flag indicating whether the
the option was negated. When the option is encountered, that function
is called to take over from get_value(). The return value should be
zero for success, -1 for usage errors.
Thanks to Stephen Boyd for API guidance.
Improved-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-12-02 07:32:16 +08:00
struct parse_opt_ctx_t ;
2019-01-27 08:35:27 +08:00
typedef enum parse_opt_result parse_opt_ll_cb ( struct parse_opt_ctx_t * ctx ,
2019-01-27 08:35:28 +08:00
const struct option * opt ,
const char * arg , int unset ) ;
parse-options: allow git commands to invent new option types
parse-options provides a variety of option behaviors, including
OPTION_CALLBACK, which should take care of just about any sane
behavior. All supported behaviors obey the following constraint:
A --foo option can only accept (and base its behavior on)
one argument, which would be the following command-line
argument in the "unsticked" form.
Alas, some existing git commands have options that do not obey that
constraint. For example, update-index --cacheinfo takes three
arguments, and update-index --resolve takes all later parameters as
arguments.
Introduces an OPTION_LOWLEVEL_CALLBACK backdoor to parse-options so
such option types can be supported without tempting inventors of other
commands through mention in the public API. Commands can set the
callback field to a function accepting three arguments: the option
parsing context, the option itself, and a flag indicating whether the
the option was negated. When the option is encountered, that function
is called to take over from get_value(). The return value should be
zero for success, -1 for usage errors.
Thanks to Stephen Boyd for API guidance.
Improved-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-12-02 07:32:16 +08:00
2007-11-05 20:03:22 +08:00
/*
* ` type ` : :
* holds the type of the option , you must have an OPTION_END last in your
* array .
*
* ` short_name ` : :
* the character to use as a short option name , ' \0 ' if none .
*
* ` long_name ` : :
* the long option name , without the leading dashes , NULL if none .
*
* ` value ` : :
* stores pointers to the values to be filled .
*
* ` argh ` : :
2021-01-06 22:44:02 +08:00
* token to explain the kind of argument this option wants . Does not
* begin in capital letter , and does not end with a full stop .
* Should be wrapped by N_ ( ) for translation .
2022-01-20 18:30:15 +08:00
* Is automatically enclosed in brackets when printed , unless it
* contains any of the following characters : ( ) < > [ ] |
* E . g . " name " is shown as " <name> " to indicate that a name value
* needs to be supplied , not the literal string " name " , but
* " <start>,<end> " and " (this|that) " are printed verbatim .
2007-11-05 20:03:22 +08:00
*
* ` help ` : :
* the short help associated to what the option does .
* Must never be NULL ( except for OPTION_END ) .
* OPTION_GROUP uses this pointer to store the group header .
2012-05-06 22:23:51 +08:00
* Should be wrapped by N_ ( ) for translation .
2007-11-05 20:03:22 +08:00
*
* ` flags ` : :
* mask of parse_opt_option_flags .
2009-04-18 02:13:30 +08:00
* PARSE_OPT_OPTARG : says that the argument is optional ( not for BOOLEANs )
2010-08-23 00:26:38 +08:00
* PARSE_OPT_NOARG : says that this option does not take an argument
2007-11-07 18:20:27 +08:00
* PARSE_OPT_NONEG : says that this option cannot be negated
2009-05-08 03:45:42 +08:00
* PARSE_OPT_HIDDEN : this option is skipped in the default usage , and
* shown only in the full usage .
2009-06-08 07:39:15 +08:00
* PARSE_OPT_LASTARG_DEFAULT : says that this option will take the default
* value if no argument is given when the option
* is last on the command line . If the option is
* not last it will require an argument .
* Should not be used with PARSE_OPT_OPTARG .
2009-05-08 03:45:42 +08:00
* PARSE_OPT_NODASH : this option doesn ' t start with a dash .
2009-05-21 15:33:17 +08:00
* PARSE_OPT_LITERAL_ARGHELP : says that argh shouldn ' t be enclosed in brackets
* ( i . e . ' < argh > ' ) in the help message .
* Useful for options with multiple parameters .
2018-02-09 19:01:40 +08:00
* PARSE_OPT_NOCOMPLETE : by default all visible options are completable
* by git - completion . bash . This option suppresses that .
2018-02-09 19:02:12 +08:00
* PARSE_OPT_COMP_ARG : this option forces to git - completion . bash to
* complete an option as - - name = not - - name even if
* the option takes optional argument .
2007-11-05 20:03:22 +08:00
*
* ` callback ` : :
2019-01-27 08:35:26 +08:00
* pointer to the callback to use for OPTION_CALLBACK
2007-11-05 20:03:22 +08:00
*
* ` defval ` : :
* default value to fill ( * - > value ) with for PARSE_OPT_OPTARG .
2015-03-29 16:32:55 +08:00
* OPTION_ { BIT , SET_INT } store the { mask , integer } to put in the value when met .
2007-11-05 20:03:22 +08:00
* CALLBACKS can use it like they want .
2019-01-27 08:35:26 +08:00
*
* ` ll_callback ` : :
* pointer to the callback to use for OPTION_LOWLEVEL_CALLBACK
*
2007-11-05 20:03:22 +08:00
*/
2007-10-15 07:35:37 +08:00
struct option {
enum parse_opt_type type ;
int short_name ;
const char * long_name ;
void * value ;
2007-10-15 07:38:30 +08:00
const char * argh ;
const char * help ;
2007-10-15 07:45:45 +08:00
2021-10-09 03:07:41 +08:00
enum parse_opt_option_flags flags ;
2007-10-15 07:45:45 +08:00
parse_opt_cb * callback ;
intptr_t defval ;
2019-01-27 08:35:26 +08:00
parse_opt_ll_cb * ll_callback ;
2019-01-27 08:35:25 +08:00
intptr_t extra ;
2007-10-15 07:35:37 +08:00
} ;
2018-02-09 19:01:41 +08:00
# define OPT_BIT_F(s, l, v, h, b, f) { OPTION_BIT, (s), (l), (v), NULL, (h), \
PARSE_OPT_NOARG | ( f ) , NULL , ( b ) }
# define OPT_COUNTUP_F(s, l, v, h, f) { OPTION_COUNTUP, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_NOARG | ( f ) }
# define OPT_SET_INT_F(s, l, v, h, i, f) { OPTION_SET_INT, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_NOARG | ( f ) , NULL , ( i ) }
# define OPT_BOOL_F(s, l, v, h, f) OPT_SET_INT_F(s, l, v, h, 1, f)
2019-01-27 08:35:33 +08:00
# define OPT_CALLBACK_F(s, l, v, a, h, f, cb) \
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , ( a ) , ( h ) , ( f ) , ( cb ) }
2019-03-24 16:20:05 +08:00
# define OPT_STRING_F(s, l, v, a, h, f) { OPTION_STRING, (s), (l), (v), (a), (h), (f) }
2019-03-24 16:20:08 +08:00
# define OPT_INTEGER_F(s, l, v, h, f) { OPTION_INTEGER, (s), (l), (v), N_("n"), (h), (f) }
2018-02-09 19:01:41 +08:00
2007-10-15 07:35:37 +08:00
# define OPT_END() { OPTION_END }
2007-10-15 07:38:30 +08:00
# define OPT_GROUP(h) { OPTION_GROUP, 0, NULL, NULL, NULL, (h) }
2018-02-09 19:01:41 +08:00
# define OPT_BIT(s, l, v, h, b) OPT_BIT_F(s, l, v, h, b, 0)
2019-01-27 08:35:25 +08:00
# define OPT_BITOP(s, l, v, h, set, clear) { OPTION_BITOP, (s), (l), (v), NULL, (h), \
PARSE_OPT_NOARG | PARSE_OPT_NONEG , NULL , \
2019-01-27 08:35:26 +08:00
( set ) , NULL , ( clear ) }
2009-06-05 07:43:57 +08:00
# define OPT_NEGBIT(s, l, v, h, b) { OPTION_NEGBIT, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_NOARG , NULL , ( b ) }
2018-02-09 19:01:41 +08:00
# define OPT_COUNTUP(s, l, v, h) OPT_COUNTUP_F(s, l, v, h, 0)
# define OPT_SET_INT(s, l, v, h, i) OPT_SET_INT_F(s, l, v, h, i, 0)
# define OPT_BOOL(s, l, v, h) OPT_BOOL_F(s, l, v, h, 0)
2013-08-03 19:51:18 +08:00
# define OPT_HIDDEN_BOOL(s, l, v, h) { OPTION_SET_INT, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_NOARG | PARSE_OPT_HIDDEN , NULL , 1 }
2021-09-22 06:40:36 +08:00
# define OPT_CMDMODE_F(s, l, v, h, i, f) { OPTION_SET_INT, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_CMDMODE | PARSE_OPT_NOARG | PARSE_OPT_NONEG | ( f ) , NULL , ( i ) }
# define OPT_CMDMODE(s, l, v, h, i) OPT_CMDMODE_F(s, l, v, h, i, 0)
2019-03-24 16:20:08 +08:00
# define OPT_INTEGER(s, l, v, h) OPT_INTEGER_F(s, l, v, h, 0)
2015-06-22 02:25:44 +08:00
# define OPT_MAGNITUDE(s, l, v, h) { OPTION_MAGNITUDE, (s), (l), (v), \
N_ ( " n " ) , ( h ) , PARSE_OPT_NONEG }
2019-03-24 16:20:05 +08:00
# define OPT_STRING(s, l, v, a, h) OPT_STRING_F(s, l, v, a, h, 0)
2011-06-09 23:55:23 +08:00
# define OPT_STRING_LIST(s, l, v, a, h) \
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , ( a ) , \
( h ) , 0 , & parse_opt_string_list }
2018-03-07 09:05:01 +08:00
# define OPT_UYN(s, l, v, h) { OPTION_CALLBACK, (s), (l), (v), NULL, \
( h ) , PARSE_OPT_NOARG , & parse_opt_tertiary }
2013-04-26 02:13:49 +08:00
# define OPT_EXPIRY_DATE(s, l, v, h) \
2014-03-24 06:58:12 +08:00
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , N_ ( " expiry-date " ) , ( h ) , 0 , \
2013-04-26 02:13:49 +08:00
parse_opt_expiry_date_cb }
2019-01-27 08:35:33 +08:00
# define OPT_CALLBACK(s, l, v, a, h, f) OPT_CALLBACK_F(s, l, v, a, h, 0, f)
2009-05-08 03:45:08 +08:00
# define OPT_NUMBER_CALLBACK(v, h, f) \
{ OPTION_NUMBER , 0 , NULL , ( v ) , NULL , ( h ) , \
PARSE_OPT_NOARG | PARSE_OPT_NONEG , ( f ) }
2009-05-24 02:53:13 +08:00
# define OPT_FILENAME(s, l, v, h) { OPTION_FILENAME, (s), (l), (v), \
2012-05-06 22:23:51 +08:00
N_ ( " file " ) , ( h ) }
Add an optional argument for --color options
Make git-branch, git-show-branch, git-grep, and all the diff-based
programs accept an optional argument <when> for --color. The argument
is a colorbool: "always", "never", or "auto". If no argument is given,
"always" is used; --no-color is an alias for --color=never. This makes
the command-line interface consistent with other GNU tools, such as `ls'
and `grep', and with the git-config color options. Note that, without
an argument, --color and --no-color work exactly as before.
To implement this, two internal changes were made:
1. Allow the first argument of git_config_colorbool() to be NULL,
in which case it returns -1 if the argument isn't "always", "never",
or "auto".
2. Add OPT_COLOR_FLAG(), OPT__COLOR(), and parse_opt_color_flag_cb()
to the option parsing library. The callback uses
git_config_colorbool(), so color.h is now a dependency
of parse-options.c.
Signed-off-by: Mark Lodato <lodatom@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-17 12:55:58 +08:00
# define OPT_COLOR_FLAG(s, l, v, h) \
2012-05-06 22:23:51 +08:00
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , N_ ( " when " ) , ( h ) , PARSE_OPT_OPTARG , \
Add an optional argument for --color options
Make git-branch, git-show-branch, git-grep, and all the diff-based
programs accept an optional argument <when> for --color. The argument
is a colorbool: "always", "never", or "auto". If no argument is given,
"always" is used; --no-color is an alias for --color=never. This makes
the command-line interface consistent with other GNU tools, such as `ls'
and `grep', and with the git-config color options. Note that, without
an argument, --color and --no-color work exactly as before.
To implement this, two internal changes were made:
1. Allow the first argument of git_config_colorbool() to be NULL,
in which case it returns -1 if the argument isn't "always", "never",
or "auto".
2. Add OPT_COLOR_FLAG(), OPT__COLOR(), and parse_opt_color_flag_cb()
to the option parsing library. The callback uses
git_config_colorbool(), so color.h is now a dependency
of parse-options.c.
Signed-off-by: Mark Lodato <lodatom@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-17 12:55:58 +08:00
parse_opt_color_flag_cb , ( intptr_t ) " always " }
2011-09-29 01:44:30 +08:00
# define OPT_NOOP_NOARG(s, l) \
{ OPTION_CALLBACK , ( s ) , ( l ) , NULL , NULL , \
2012-05-06 22:23:51 +08:00
N_ ( " no-op (backward compatibility) " ) , \
2011-09-29 01:44:30 +08:00
PARSE_OPT_HIDDEN | PARSE_OPT_NOARG , parse_opt_noop_cb }
2019-04-29 18:05:25 +08:00
# define OPT_ALIAS(s, l, source_long_name) \
{ OPTION_ALIAS , ( s ) , ( l ) , ( source_long_name ) }
2019-01-27 08:35:23 +08:00
/*
* parse_options ( ) will filter out the processed options and leave the
* non - option arguments in argv [ ] . argv0 is assumed program name and
* skipped .
*
* usagestr strings should be marked for translation with N_ ( ) .
*
2007-10-15 07:35:37 +08:00
* Returns the number of arguments left in argv [ ] .
2019-01-27 08:35:23 +08:00
*
* In one - shot mode , argv0 is not a program name , argv [ ] is left
* untouched and parse_options ( ) returns the number of options
* processed .
2007-10-15 07:35:37 +08:00
*/
2021-11-09 19:04:43 +08:00
int parse_options ( int argc , const char * * argv , const char * prefix ,
const struct option * options ,
const char * const usagestr [ ] ,
enum parse_opt_flags flags ) ;
2007-10-15 07:38:30 +08:00
2019-01-17 21:05:00 +08:00
NORETURN void usage_with_options ( const char * const * usagestr ,
const struct option * options ) ;
2007-10-15 07:35:37 +08:00
2019-01-17 21:05:00 +08:00
NORETURN void usage_msg_opt ( const char * msg ,
const char * const * usagestr ,
const struct option * options ) ;
2009-02-02 13:12:58 +08:00
2021-12-28 21:28:43 +08:00
/**
* usage_msg_optf ( ) is like usage_msg_opt ( ) except that the first
* argument is a format string , and optional format arguments follow
* after the 3 rd option .
*/
__attribute__ ( ( format ( printf , 1 , 4 ) ) )
void NORETURN usage_msg_optf ( const char * fmt ,
const char * const * usagestr ,
const struct option * options , . . . ) ;
2022-02-01 06:07:46 +08:00
void die_for_incompatible_opt4 ( int opt1 , const char * opt1_name ,
int opt2 , const char * opt2_name ,
int opt3 , const char * opt3_name ,
int opt4 , const char * opt4_name ) ;
static inline void die_for_incompatible_opt3 ( int opt1 , const char * opt1_name ,
int opt2 , const char * opt2_name ,
int opt3 , const char * opt3_name )
{
die_for_incompatible_opt4 ( opt1 , opt1_name ,
opt2 , opt2_name ,
opt3 , opt3_name ,
0 , " " ) ;
}
assert NOARG/NONEG behavior of parse-options callbacks
When we define a parse-options callback, the flags we put in the option
struct must match what the callback expects. For example, a callback
which does not handle the "unset" parameter should only be used with
PARSE_OPT_NONEG. But since the callback and the option struct are not
defined next to each other, it's easy to get this wrong (as earlier
patches in this series show).
Fortunately, the compiler can help us here: compiling with
-Wunused-parameters can show us which callbacks ignore their "unset"
parameters (and likewise, ones that ignore "arg" expect to be triggered
with PARSE_OPT_NOARG).
But after we've inspected a callback and determined that all of its
callers use the right flags, what do we do next? We'd like to silence
the compiler warning, but do so in a way that will catch any wrong calls
in the future.
We can do that by actually checking those variables and asserting that
they match our expectations. Because this is such a common pattern,
we'll introduce some helper macros. The resulting messages aren't
as descriptive as we could make them, but the file/line information from
BUG() is enough to identify the problem (and anyway, the point is that
these should never be seen).
Each of the annotated callbacks in this patch triggers
-Wunused-parameters, and was manually inspected to make sure all callers
use the correct options (so none of these BUGs should be triggerable).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-11-05 14:45:42 +08:00
/*
* Use these assertions for callbacks that expect to be called with NONEG and
* NOARG respectively , and do not otherwise handle the " unset " and " arg "
* parameters .
*/
# define BUG_ON_OPT_NEG(unset) do { \
if ( ( unset ) ) \
BUG ( " option callback does not expect negation " ) ; \
} while ( 0 )
# define BUG_ON_OPT_ARG(arg) do { \
if ( ( arg ) ) \
BUG ( " option callback does not expect an argument " ) ; \
} while ( 0 )
2019-03-07 23:44:09 +08:00
/*
* Similar to the assertions above , but checks that " arg " is always non - NULL .
* This assertion also implies BUG_ON_OPT_NEG ( ) , letting you declare both
* assertions in a single line .
*/
# define BUG_ON_OPT_NEG_NOARG(unset, arg) do { \
BUG_ON_OPT_NEG ( unset ) ; \
if ( ! ( arg ) ) \
BUG ( " option callback expects an argument " ) ; \
} while ( 0 )
2009-04-18 02:13:30 +08:00
/*----- incremental advanced APIs -----*/
2008-06-24 03:59:37 +08:00
2008-06-24 04:55:11 +08:00
/*
* It ' s okay for the caller to consume argv / argc in the usual way .
* Other fields of that structure are private to parse - options and should not
* be modified in any way .
*/
2008-06-24 03:59:37 +08:00
struct parse_opt_ctx_t {
const char * * argv ;
const char * * out ;
2015-11-17 18:25:38 +08:00
int argc , cpidx , total ;
2008-06-24 03:59:37 +08:00
const char * opt ;
2021-10-09 03:07:38 +08:00
enum parse_opt_flags flags ;
2009-05-24 02:53:12 +08:00
const char * prefix ;
2019-04-29 18:05:25 +08:00
const char * * alias_groups ; /* must be in groups of 3 elements! */
struct option * updated_options ;
2008-06-24 03:59:37 +08:00
} ;
2019-01-17 21:05:00 +08:00
void parse_options_start ( struct parse_opt_ctx_t * ctx ,
int argc , const char * * argv , const char * prefix ,
2021-10-09 03:07:38 +08:00
const struct option * options ,
enum parse_opt_flags flags ) ;
2008-06-24 03:59:37 +08:00
2021-10-09 03:07:39 +08:00
enum parse_opt_result parse_options_step ( struct parse_opt_ctx_t * ctx ,
const struct option * options ,
const char * const usagestr [ ] ) ;
2008-06-24 04:38:58 +08:00
2019-01-17 21:05:00 +08:00
int parse_options_end ( struct parse_opt_ctx_t * ctx ) ;
2008-06-24 03:59:37 +08:00
2019-03-29 18:39:04 +08:00
struct option * parse_options_dup ( const struct option * a ) ;
2020-02-09 23:57:56 +08:00
struct option * parse_options_concat ( const struct option * a , const struct option * b ) ;
2008-06-24 03:59:37 +08:00
2007-10-14 17:05:12 +08:00
/*----- some often used options -----*/
2019-01-17 21:05:00 +08:00
int parse_opt_abbrev_cb ( const struct option * , const char * , int ) ;
int parse_opt_expiry_date_cb ( const struct option * , const char * , int ) ;
int parse_opt_color_flag_cb ( const struct option * , const char * , int ) ;
int parse_opt_verbosity_cb ( const struct option * , const char * , int ) ;
2019-04-17 22:30:40 +08:00
/* value is struct oid_array* */
2019-01-17 21:05:00 +08:00
int parse_opt_object_name ( const struct option * , const char * , int ) ;
2019-04-17 22:30:40 +08:00
/* value is struct object_id* */
int parse_opt_object_id ( const struct option * , const char * , int ) ;
2019-01-17 21:05:00 +08:00
int parse_opt_commits ( const struct option * , const char * , int ) ;
2019-04-17 22:30:39 +08:00
int parse_opt_commit ( const struct option * , const char * , int ) ;
2019-01-17 21:05:00 +08:00
int parse_opt_tertiary ( const struct option * , const char * , int ) ;
int parse_opt_string_list ( const struct option * , const char * , int ) ;
int parse_opt_noop_cb ( const struct option * , const char * , int ) ;
2019-05-14 06:43:17 +08:00
enum parse_opt_result parse_opt_unknown_cb ( struct parse_opt_ctx_t * ctx ,
const struct option * ,
const char * , int ) ;
2019-01-17 21:05:00 +08:00
int parse_opt_passthru ( const struct option * , const char * , int ) ;
int parse_opt_passthru_argv ( const struct option * , const char * , int ) ;
branch: add flags and config to inherit tracking
It can be helpful when creating a new branch to use the existing
tracking configuration from the branch point. However, there is
currently not a method to automatically do so.
Teach git-{branch,checkout,switch} an "inherit" argument to the
"--track" option. When this is set, creating a new branch will cause the
tracking configuration to default to the configuration of the branch
point, if set.
For example, if branch "main" tracks "origin/main", and we run
`git checkout --track=inherit -b feature main`, then branch "feature"
will track "origin/main". Thus, `git status` will show us how far
ahead/behind we are from origin, and `git pull` will pull from origin.
This is particularly useful when creating branches across many
submodules, such as with `git submodule foreach ...` (or if running with
a patch such as [1], which we use at $job), as it avoids having to
manually set tracking info for each submodule.
Since we've added an argument to "--track", also add "--track=direct" as
another way to explicitly get the original "--track" behavior ("--track"
without an argument still works as well).
Finally, teach branch.autoSetupMerge a new "inherit" option. When this
is set, "--track=inherit" becomes the default behavior.
[1]: https://lore.kernel.org/git/20180927221603.148025-1-sbeller@google.com/
Signed-off-by: Josh Steadmon <steadmon@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-12-21 11:30:23 +08:00
/* value is enum branch_track* */
int parse_opt_tracking_mode ( const struct option * , const char * , int ) ;
2007-10-14 17:05:12 +08:00
2013-12-07 13:02:53 +08:00
# define OPT__VERBOSE(var, h) OPT_COUNTUP('v', "verbose", (var), (h))
# define OPT__QUIET(var, h) OPT_COUNTUP('q', "quiet", (var), (h))
2008-11-15 08:14:24 +08:00
# define OPT__VERBOSITY(var) \
2012-05-06 22:23:51 +08:00
{ OPTION_CALLBACK , ' v ' , " verbose " , ( var ) , NULL , N_ ( " be more verbose " ) , \
2008-11-15 08:14:24 +08:00
PARSE_OPT_NOARG , & parse_opt_verbosity_cb , 0 } , \
2012-05-06 22:23:51 +08:00
{ OPTION_CALLBACK , ' q ' , " quiet " , ( var ) , NULL , N_ ( " be more quiet " ) , \
2008-11-15 08:14:24 +08:00
PARSE_OPT_NOARG , & parse_opt_verbosity_cb , 0 }
2013-12-07 13:02:53 +08:00
# define OPT__DRY_RUN(var, h) OPT_BOOL('n', "dry-run", (var), (h))
2018-02-09 19:01:42 +08:00
# define OPT__FORCE(var, h, f) OPT_COUNTUP_F('f', "force", (var), (h), (f))
2007-10-14 17:05:12 +08:00
# define OPT__ABBREV(var) \
2012-05-06 22:23:51 +08:00
{ OPTION_CALLBACK , 0 , " abbrev " , ( var ) , N_ ( " n " ) , \
2020-08-14 09:07:12 +08:00
N_ ( " use <n> digits to display object names " ) , \
2007-10-14 17:05:12 +08:00
PARSE_OPT_OPTARG , & parse_opt_abbrev_cb , 0 }
Add an optional argument for --color options
Make git-branch, git-show-branch, git-grep, and all the diff-based
programs accept an optional argument <when> for --color. The argument
is a colorbool: "always", "never", or "auto". If no argument is given,
"always" is used; --no-color is an alias for --color=never. This makes
the command-line interface consistent with other GNU tools, such as `ls'
and `grep', and with the git-config color options. Note that, without
an argument, --color and --no-color work exactly as before.
To implement this, two internal changes were made:
1. Allow the first argument of git_config_colorbool() to be NULL,
in which case it returns -1 if the argument isn't "always", "never",
or "auto".
2. Add OPT_COLOR_FLAG(), OPT__COLOR(), and parse_opt_color_flag_cb()
to the option parsing library. The callback uses
git_config_colorbool(), so color.h is now a dependency
of parse-options.c.
Signed-off-by: Mark Lodato <lodatom@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-17 12:55:58 +08:00
# define OPT__COLOR(var, h) \
OPT_COLOR_FLAG ( 0 , " color " , ( var ) , ( h ) )
2012-04-21 12:44:32 +08:00
# define OPT_COLUMN(s, l, v, h) \
2012-08-20 20:31:50 +08:00
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , N_ ( " style " ) , ( h ) , PARSE_OPT_OPTARG , parseopt_column_callback }
2015-06-14 16:41:48 +08:00
# define OPT_PASSTHRU(s, l, v, a, h, f) \
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , ( a ) , ( h ) , ( f ) , parse_opt_passthru }
2015-06-14 16:41:49 +08:00
# define OPT_PASSTHRU_ARGV(s, l, v, a, h, f) \
{ OPTION_CALLBACK , ( s ) , ( l ) , ( v ) , ( a ) , ( h ) , ( f ) , parse_opt_passthru_argv }
2015-07-08 00:06:15 +08:00
# define _OPT_CONTAINS_OR_WITH(name, variable, help, flag) \
{ OPTION_CALLBACK , 0 , name , ( variable ) , N_ ( " commit " ) , ( help ) , \
PARSE_OPT_LASTARG_DEFAULT | flag , \
parse_opt_commits , ( intptr_t ) " HEAD " \
}
2017-03-25 02:40:53 +08:00
# define OPT_CONTAINS(v, h) _OPT_CONTAINS_OR_WITH("contains", v, h, PARSE_OPT_NONEG)
ref-filter: add --no-contains option to tag/branch/for-each-ref
Change the tag, branch & for-each-ref commands to have a --no-contains
option in addition to their longstanding --contains options.
This allows for finding the last-good rollout tag given a known-bad
<commit>. Given a hypothetically bad commit cf5c7253e0, the git
version to revert to can be found with this hacky two-liner:
(git tag -l 'v[0-9]*'; git tag -l --contains cf5c7253e0 'v[0-9]*') |
sort | uniq -c | grep -E '^ *1 ' | awk '{print $2}' | tail -n 10
With this new --no-contains option the same can be achieved with:
git tag -l --no-contains cf5c7253e0 'v[0-9]*' | sort | tail -n 10
As the filtering machinery is shared between the tag, branch &
for-each-ref commands, implement this for those commands too. A
practical use for this with "branch" is e.g. finding branches which
were branched off between v2.8.0 and v2.10.0:
git branch --contains v2.8.0 --no-contains v2.10.0
The "describe" command also has a --contains option, but its semantics
are unrelated to what tag/branch/for-each-ref use --contains for. A
--no-contains option for "describe" wouldn't make any sense, other
than being exactly equivalent to not supplying --contains at all,
which would be confusing at best.
Add a --without option to "tag" as an alias for --no-contains, for
consistency with --with and --contains. The --with option is
undocumented, and possibly the only user of it is
Junio (<xmqqefy71iej.fsf@gitster.mtv.corp.google.com>). But it's
trivial to support, so let's do that.
The additions to the the test suite are inverse copies of the
corresponding --contains tests. With this change --no-contains for
tag, branch & for-each-ref is just as well tested as the existing
--contains option.
In addition to those tests, add a test for "tag" which asserts that
--no-contains won't find tree/blob tags, which is slightly
unintuitive, but consistent with how --contains works & is documented.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-03-25 02:40:57 +08:00
# define OPT_NO_CONTAINS(v, h) _OPT_CONTAINS_OR_WITH("no-contains", v, h, PARSE_OPT_NONEG)
2017-03-25 02:40:53 +08:00
# define OPT_WITH(v, h) _OPT_CONTAINS_OR_WITH("with", v, h, PARSE_OPT_HIDDEN | PARSE_OPT_NONEG)
ref-filter: add --no-contains option to tag/branch/for-each-ref
Change the tag, branch & for-each-ref commands to have a --no-contains
option in addition to their longstanding --contains options.
This allows for finding the last-good rollout tag given a known-bad
<commit>. Given a hypothetically bad commit cf5c7253e0, the git
version to revert to can be found with this hacky two-liner:
(git tag -l 'v[0-9]*'; git tag -l --contains cf5c7253e0 'v[0-9]*') |
sort | uniq -c | grep -E '^ *1 ' | awk '{print $2}' | tail -n 10
With this new --no-contains option the same can be achieved with:
git tag -l --no-contains cf5c7253e0 'v[0-9]*' | sort | tail -n 10
As the filtering machinery is shared between the tag, branch &
for-each-ref commands, implement this for those commands too. A
practical use for this with "branch" is e.g. finding branches which
were branched off between v2.8.0 and v2.10.0:
git branch --contains v2.8.0 --no-contains v2.10.0
The "describe" command also has a --contains option, but its semantics
are unrelated to what tag/branch/for-each-ref use --contains for. A
--no-contains option for "describe" wouldn't make any sense, other
than being exactly equivalent to not supplying --contains at all,
which would be confusing at best.
Add a --without option to "tag" as an alias for --no-contains, for
consistency with --with and --contains. The --with option is
undocumented, and possibly the only user of it is
Junio (<xmqqefy71iej.fsf@gitster.mtv.corp.google.com>). But it's
trivial to support, so let's do that.
The additions to the the test suite are inverse copies of the
corresponding --contains tests. With this change --no-contains for
tag, branch & for-each-ref is just as well tested as the existing
--contains option.
In addition to those tests, add a test for "tag" which asserts that
--no-contains won't find tree/blob tags, which is slightly
unintuitive, but consistent with how --contains works & is documented.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-03-25 02:40:57 +08:00
# define OPT_WITHOUT(v, h) _OPT_CONTAINS_OR_WITH("without", v, h, PARSE_OPT_HIDDEN | PARSE_OPT_NONEG)
2019-04-17 18:23:26 +08:00
# define OPT_CLEANUP(v) OPT_STRING(0, "cleanup", v, N_("mode"), N_("how to strip spaces and #comments from message"))
2019-11-06 23:51:13 +08:00
# define OPT_PATHSPEC_FROM_FILE(v) OPT_FILENAME(0, "pathspec-from-file", v, N_("read pathspec from file"))
# define OPT_PATHSPEC_FILE_NUL(v) OPT_BOOL(0, "pathspec-file-nul", v, N_("with --pathspec-from-file, pathspec elements are separated with NUL character"))
2020-04-07 22:28:07 +08:00
# define OPT_AUTOSTASH(v) OPT_BOOL(0, "autostash", v, N_("automatically stash / stash pop before and after"))
2007-10-14 17:05:12 +08:00
2007-10-15 07:35:37 +08:00
# endif