2008-08-02 16:08:38 +08:00
|
|
|
/*
|
|
|
|
* Builtin help command
|
|
|
|
*/
|
|
|
|
#include "builtin.h"
|
2023-05-16 14:33:57 +08:00
|
|
|
#include "config.h"
|
2018-04-11 05:26:18 +08:00
|
|
|
#include "exec-cmd.h"
|
2023-03-21 14:25:54 +08:00
|
|
|
#include "gettext.h"
|
2023-04-11 15:41:59 +08:00
|
|
|
#include "pager.h"
|
2008-08-02 16:08:38 +08:00
|
|
|
#include "parse-options.h"
|
2023-04-23 04:17:20 +08:00
|
|
|
#include "path.h"
|
2008-08-02 16:08:38 +08:00
|
|
|
#include "run-command.h"
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
#include "config-list.h"
|
2008-08-02 16:08:38 +08:00
|
|
|
#include "help.h"
|
2018-05-21 02:40:06 +08:00
|
|
|
#include "alias.h"
|
2023-03-21 14:26:05 +08:00
|
|
|
#include "setup.h"
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2012-06-07 04:28:16 +08:00
|
|
|
#ifndef DEFAULT_HELP_FORMAT
|
|
|
|
#define DEFAULT_HELP_FORMAT "man"
|
|
|
|
#endif
|
|
|
|
|
2008-08-02 16:08:38 +08:00
|
|
|
static struct man_viewer_list {
|
|
|
|
struct man_viewer_list *next;
|
|
|
|
char name[FLEX_ARRAY];
|
|
|
|
} *man_viewer_list;
|
|
|
|
|
|
|
|
static struct man_viewer_info_list {
|
|
|
|
struct man_viewer_info_list *next;
|
|
|
|
const char *info;
|
|
|
|
char name[FLEX_ARRAY];
|
|
|
|
} *man_viewer_info_list;
|
|
|
|
|
|
|
|
enum help_format {
|
2010-01-09 13:10:05 +08:00
|
|
|
HELP_FORMAT_NONE,
|
2008-08-02 16:08:38 +08:00
|
|
|
HELP_FORMAT_MAN,
|
|
|
|
HELP_FORMAT_INFO,
|
2010-05-14 17:31:35 +08:00
|
|
|
HELP_FORMAT_WEB
|
2008-08-02 16:08:38 +08:00
|
|
|
};
|
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
enum show_config_type {
|
|
|
|
SHOW_CONFIG_HUMAN,
|
|
|
|
SHOW_CONFIG_VARS,
|
|
|
|
SHOW_CONFIG_SECTIONS,
|
|
|
|
};
|
|
|
|
|
2021-09-22 06:40:36 +08:00
|
|
|
static enum help_action {
|
|
|
|
HELP_ACTION_ALL = 1,
|
|
|
|
HELP_ACTION_GUIDES,
|
|
|
|
HELP_ACTION_CONFIG,
|
2022-08-05 00:28:33 +08:00
|
|
|
HELP_ACTION_USER_INTERFACES,
|
2022-08-05 00:28:34 +08:00
|
|
|
HELP_ACTION_DEVELOPER_INTERFACES,
|
2021-09-22 06:40:36 +08:00
|
|
|
HELP_ACTION_CONFIG_FOR_COMPLETION,
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
HELP_ACTION_CONFIG_SECTIONS_FOR_COMPLETION,
|
2021-09-22 06:40:36 +08:00
|
|
|
} cmd_mode;
|
2012-06-28 14:58:02 +08:00
|
|
|
|
2021-09-22 06:40:36 +08:00
|
|
|
static const char *html_path;
|
2018-09-29 14:08:14 +08:00
|
|
|
static int verbose = 1;
|
2010-01-09 13:10:05 +08:00
|
|
|
static enum help_format help_format = HELP_FORMAT_NONE;
|
2016-08-27 01:58:35 +08:00
|
|
|
static int exclude_guides;
|
2022-02-22 03:38:51 +08:00
|
|
|
static int show_external_commands = -1;
|
|
|
|
static int show_aliases = -1;
|
2008-08-02 16:08:38 +08:00
|
|
|
static struct option builtin_help_options[] = {
|
2021-09-22 06:40:36 +08:00
|
|
|
OPT_CMDMODE('a', "all", &cmd_mode, N_("print all available commands"),
|
|
|
|
HELP_ACTION_ALL),
|
2022-02-22 03:38:51 +08:00
|
|
|
OPT_BOOL(0, "external-commands", &show_external_commands,
|
|
|
|
N_("show external commands in --all")),
|
|
|
|
OPT_BOOL(0, "aliases", &show_aliases, N_("show aliases in --all")),
|
2016-08-27 01:58:35 +08:00
|
|
|
OPT_HIDDEN_BOOL(0, "exclude-guides", &exclude_guides, N_("exclude guides")),
|
2012-08-20 20:32:17 +08:00
|
|
|
OPT_SET_INT('m', "man", &help_format, N_("show man page"), HELP_FORMAT_MAN),
|
|
|
|
OPT_SET_INT('w', "web", &help_format, N_("show manual in web browser"),
|
2008-08-02 16:08:38 +08:00
|
|
|
HELP_FORMAT_WEB),
|
2012-08-20 20:32:17 +08:00
|
|
|
OPT_SET_INT('i', "info", &help_format, N_("show info page"),
|
2008-08-02 16:08:38 +08:00
|
|
|
HELP_FORMAT_INFO),
|
2018-05-21 02:40:01 +08:00
|
|
|
OPT__VERBOSE(&verbose, N_("print command description")),
|
2021-09-22 06:40:36 +08:00
|
|
|
|
|
|
|
OPT_CMDMODE('g', "guides", &cmd_mode, N_("print list of useful guides"),
|
|
|
|
HELP_ACTION_GUIDES),
|
2022-08-05 00:28:33 +08:00
|
|
|
OPT_CMDMODE(0, "user-interfaces", &cmd_mode,
|
|
|
|
N_("print list of user-facing repository, command and file interfaces"),
|
|
|
|
HELP_ACTION_USER_INTERFACES),
|
2022-08-05 00:28:34 +08:00
|
|
|
OPT_CMDMODE(0, "developer-interfaces", &cmd_mode,
|
|
|
|
N_("print list of file formats, protocols and other developer interfaces"),
|
|
|
|
HELP_ACTION_DEVELOPER_INTERFACES),
|
2021-09-22 06:40:36 +08:00
|
|
|
OPT_CMDMODE('c', "config", &cmd_mode, N_("print all configuration variable names"),
|
|
|
|
HELP_ACTION_CONFIG),
|
|
|
|
OPT_CMDMODE_F(0, "config-for-completion", &cmd_mode, "",
|
|
|
|
HELP_ACTION_CONFIG_FOR_COMPLETION, PARSE_OPT_HIDDEN),
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
OPT_CMDMODE_F(0, "config-sections-for-completion", &cmd_mode, "",
|
|
|
|
HELP_ACTION_CONFIG_SECTIONS_FOR_COMPLETION, PARSE_OPT_HIDDEN),
|
2021-09-22 06:40:36 +08:00
|
|
|
|
2008-08-02 16:08:38 +08:00
|
|
|
OPT_END(),
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char * const builtin_help_usage[] = {
|
2022-10-13 23:39:05 +08:00
|
|
|
"git help [-a|--all] [--[no-]verbose] [--[no-]external-commands] [--[no-]aliases]",
|
2022-08-05 00:28:32 +08:00
|
|
|
N_("git help [[-i|--info] [-m|--man] [-w|--web]] [<command>|<doc>]"),
|
2022-02-01 06:07:48 +08:00
|
|
|
"git help [-g|--guides]",
|
|
|
|
"git help [-c|--config]",
|
2022-08-05 00:28:33 +08:00
|
|
|
"git help [--user-interfaces]",
|
2022-08-05 00:28:34 +08:00
|
|
|
"git help [--developer-interfaces]",
|
2008-08-02 16:08:38 +08:00
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
struct slot_expansion {
|
|
|
|
const char *prefix;
|
|
|
|
const char *placeholder;
|
|
|
|
void (*fn)(struct string_list *list, const char *prefix);
|
|
|
|
int found;
|
|
|
|
};
|
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
static void list_config_help(enum show_config_type type)
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
{
|
|
|
|
struct slot_expansion slot_expansions[] = {
|
|
|
|
{ "advice", "*", list_config_advices },
|
|
|
|
{ "color.branch", "<slot>", list_config_color_branch_slots },
|
|
|
|
{ "color.decorate", "<slot>", list_config_color_decorate_slots },
|
|
|
|
{ "color.diff", "<slot>", list_config_color_diff_slots },
|
|
|
|
{ "color.grep", "<slot>", list_config_color_grep_slots },
|
|
|
|
{ "color.interactive", "<slot>", list_config_color_interactive_slots },
|
|
|
|
{ "color.remote", "<slot>", list_config_color_sideband_slots },
|
|
|
|
{ "color.status", "<slot>", list_config_color_status_slots },
|
|
|
|
{ "fsck", "<msg-id>", list_config_fsck_msg_ids },
|
|
|
|
{ "receive.fsck", "<msg-id>", list_config_fsck_msg_ids },
|
|
|
|
{ NULL, NULL, NULL }
|
|
|
|
};
|
|
|
|
const char **p;
|
|
|
|
struct slot_expansion *e;
|
|
|
|
struct string_list keys = STRING_LIST_INIT_DUP;
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
struct string_list keys_uniq = STRING_LIST_INIT_DUP;
|
|
|
|
struct string_list_item *item;
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
int i;
|
|
|
|
|
|
|
|
for (p = config_name_list; *p; p++) {
|
|
|
|
const char *var = *p;
|
|
|
|
struct strbuf sb = STRBUF_INIT;
|
|
|
|
|
|
|
|
for (e = slot_expansions; e->prefix; e++) {
|
|
|
|
|
|
|
|
strbuf_reset(&sb);
|
|
|
|
strbuf_addf(&sb, "%s.%s", e->prefix, e->placeholder);
|
|
|
|
if (!strcasecmp(var, sb.buf)) {
|
|
|
|
e->fn(&keys, e->prefix);
|
|
|
|
e->found++;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
strbuf_release(&sb);
|
|
|
|
if (!e->prefix)
|
|
|
|
string_list_append(&keys, var);
|
|
|
|
}
|
|
|
|
|
|
|
|
for (e = slot_expansions; e->prefix; e++)
|
|
|
|
if (!e->found)
|
|
|
|
BUG("slot_expansion %s.%s is not used",
|
|
|
|
e->prefix, e->placeholder);
|
|
|
|
|
|
|
|
string_list_sort(&keys);
|
|
|
|
for (i = 0; i < keys.nr; i++) {
|
|
|
|
const char *var = keys.items[i].string;
|
|
|
|
const char *wildcard, *tag, *cut;
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
const char *dot = NULL;
|
|
|
|
struct strbuf sb = STRBUF_INIT;
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
switch (type) {
|
|
|
|
case SHOW_CONFIG_HUMAN:
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
puts(var);
|
|
|
|
continue;
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
case SHOW_CONFIG_SECTIONS:
|
|
|
|
dot = strchr(var, '.');
|
|
|
|
break;
|
|
|
|
case SHOW_CONFIG_VARS:
|
|
|
|
break;
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
}
|
|
|
|
wildcard = strchr(var, '*');
|
|
|
|
tag = strchr(var, '<');
|
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
if (!dot && !wildcard && !tag) {
|
|
|
|
string_list_append(&keys_uniq, var);
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
if (dot)
|
|
|
|
cut = dot;
|
|
|
|
else if (wildcard && !tag)
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
cut = wildcard;
|
|
|
|
else if (!wildcard && tag)
|
|
|
|
cut = tag;
|
|
|
|
else
|
|
|
|
cut = wildcard < tag ? wildcard : tag;
|
|
|
|
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
strbuf_add(&sb, var, cut - var);
|
|
|
|
string_list_append(&keys_uniq, sb.buf);
|
|
|
|
strbuf_release(&sb);
|
|
|
|
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
}
|
|
|
|
string_list_clear(&keys, 0);
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
string_list_remove_duplicates(&keys_uniq, 0);
|
|
|
|
for_each_string_list_item(item, &keys_uniq)
|
|
|
|
puts(item->string);
|
|
|
|
string_list_clear(&keys_uniq, 0);
|
help: move list_config_help to builtin/help
Starting in 3ac68a93fd2, help.o began to depend on builtin/branch.o,
builtin/clean.o, and builtin/config.o. This meant that help.o was
unusable outside of the context of the main Git executable.
To make help.o usable by other commands again, move list_config_help()
into builtin/help.c (where it makes sense to assume other builtin libraries
are present).
When command-list.h is included but a member is not used, we start to
hear a compiler warning. Since the config list is generated in a fairly
different way than the command list, and since commands and config
options are semantically different, move the config list into its own
header and move the generator into its own script and build rule.
For reasons explained in 976aaedc (msvc: add a Makefile target to
pre-generate the Visual Studio solution, 2019-07-29), some build
artifacts we consider non-source files cannot be generated in the
Visual Studio environment, and we already have some Makefile tweaks
to help Visual Studio to use generated command-list.h header file.
Do the same to a new generated file, config-list.h, introduced by
this change.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
2020-04-17 05:18:03 +08:00
|
|
|
}
|
|
|
|
|
2008-08-02 16:08:38 +08:00
|
|
|
static enum help_format parse_help_format(const char *format)
|
|
|
|
{
|
|
|
|
if (!strcmp(format, "man"))
|
|
|
|
return HELP_FORMAT_MAN;
|
|
|
|
if (!strcmp(format, "info"))
|
|
|
|
return HELP_FORMAT_INFO;
|
|
|
|
if (!strcmp(format, "web") || !strcmp(format, "html"))
|
|
|
|
return HELP_FORMAT_WEB;
|
2019-02-16 19:24:41 +08:00
|
|
|
/*
|
|
|
|
* Please update _git_config() in git-completion.bash when you
|
|
|
|
* add new help formats.
|
|
|
|
*/
|
2012-04-23 20:30:24 +08:00
|
|
|
die(_("unrecognized help format '%s'"), format);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static const char *get_man_viewer_info(const char *name)
|
|
|
|
{
|
|
|
|
struct man_viewer_info_list *viewer;
|
|
|
|
|
|
|
|
for (viewer = man_viewer_info_list; viewer; viewer = viewer->next)
|
|
|
|
{
|
|
|
|
if (!strcasecmp(name, viewer->name))
|
|
|
|
return viewer->info;
|
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int check_emacsclient_version(void)
|
|
|
|
{
|
|
|
|
struct strbuf buffer = STRBUF_INIT;
|
2014-08-20 03:09:35 +08:00
|
|
|
struct child_process ec_process = CHILD_PROCESS_INIT;
|
2008-08-02 16:08:38 +08:00
|
|
|
int version;
|
|
|
|
|
|
|
|
/* emacsclient prints its version number on stderr */
|
2021-11-26 06:52:20 +08:00
|
|
|
strvec_pushl(&ec_process.args, "emacsclient", "--version", NULL);
|
2008-08-02 16:08:38 +08:00
|
|
|
ec_process.err = -1;
|
|
|
|
ec_process.stdout_to_stderr = 1;
|
2009-06-09 04:34:31 +08:00
|
|
|
if (start_command(&ec_process))
|
2012-04-23 20:30:24 +08:00
|
|
|
return error(_("Failed to start emacsclient."));
|
2009-06-09 04:34:31 +08:00
|
|
|
|
2008-08-02 16:08:38 +08:00
|
|
|
strbuf_read(&buffer, ec_process.err, 20);
|
|
|
|
close(ec_process.err);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Don't bother checking return value, because "emacsclient --version"
|
|
|
|
* seems to always exits with code 1.
|
|
|
|
*/
|
|
|
|
finish_command(&ec_process);
|
|
|
|
|
2013-12-01 04:55:40 +08:00
|
|
|
if (!starts_with(buffer.buf, "emacsclient")) {
|
2008-08-02 16:08:38 +08:00
|
|
|
strbuf_release(&buffer);
|
2012-04-23 20:30:24 +08:00
|
|
|
return error(_("Failed to parse emacsclient version."));
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
strbuf_remove(&buffer, 0, strlen("emacsclient"));
|
|
|
|
version = atoi(buffer.buf);
|
|
|
|
|
|
|
|
if (version < 22) {
|
|
|
|
strbuf_release(&buffer);
|
2012-04-23 20:30:24 +08:00
|
|
|
return error(_("emacsclient version '%d' too old (< 22)."),
|
2009-06-09 04:34:31 +08:00
|
|
|
version);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
strbuf_release(&buffer);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-05-01 17:06:36 +08:00
|
|
|
static void exec_woman_emacs(const char *path, const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
if (!check_emacsclient_version()) {
|
|
|
|
/* This works only with emacsclient version >= 22. */
|
|
|
|
struct strbuf man_page = STRBUF_INIT;
|
|
|
|
|
|
|
|
if (!path)
|
|
|
|
path = "emacsclient";
|
|
|
|
strbuf_addf(&man_page, "(woman \"%s\")", page);
|
2010-07-24 23:20:23 +08:00
|
|
|
execlp(path, "emacsclient", "-e", man_page.buf, (char *)NULL);
|
2016-05-08 17:47:27 +08:00
|
|
|
warning_errno(_("failed to exec '%s'"), path);
|
2017-08-31 01:49:46 +08:00
|
|
|
strbuf_release(&man_page);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-05-01 17:06:36 +08:00
|
|
|
static void exec_man_konqueror(const char *path, const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
const char *display = getenv("DISPLAY");
|
|
|
|
if (display && *display) {
|
|
|
|
struct strbuf man_page = STRBUF_INIT;
|
|
|
|
const char *filename = "kfmclient";
|
|
|
|
|
|
|
|
/* It's simpler to launch konqueror using kfmclient. */
|
|
|
|
if (path) {
|
help: clean up kfmclient munging
When we are going to launch "/path/to/konqueror", we instead
rewrite this into "/path/to/kfmclient" by duplicating the
original string and writing over the ending bits. This can
be done more obviously with strip_suffix and xstrfmt.
Note that we also fix a subtle bug with the "filename"
parameter, which is passed as argv[0] to the child. If the
user has configured a program name with no directory
component, we always pass the string "kfmclient", even if
your program is called something else. But if you give a
full path, we give the basename of that path. But more
bizarrely, if we rewrite "konqueror" to "kfmclient", we
still pass "konqueror".
The history of this function doesn't reveal anything
interesting, so it looks like just an oversight from
combining the suffix-munging with the basename-finding.
Let's just call basename on the munged path, which produces
consistent results (if you gave a program, whether a full
path or not, we pass its basename).
Probably this doesn't matter at all in practice, but it
makes the code slightly less confusing to read.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-09-25 05:08:16 +08:00
|
|
|
size_t len;
|
|
|
|
if (strip_suffix(path, "/konqueror", &len))
|
|
|
|
path = xstrfmt("%.*s/kfmclient", (int)len, path);
|
|
|
|
filename = basename((char *)path);
|
2008-08-02 16:08:38 +08:00
|
|
|
} else
|
|
|
|
path = "kfmclient";
|
|
|
|
strbuf_addf(&man_page, "man:%s(1)", page);
|
2010-07-24 23:20:23 +08:00
|
|
|
execlp(path, filename, "newTab", man_page.buf, (char *)NULL);
|
2016-05-08 17:47:27 +08:00
|
|
|
warning_errno(_("failed to exec '%s'"), path);
|
2017-08-31 01:49:44 +08:00
|
|
|
strbuf_release(&man_page);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-05-01 17:06:36 +08:00
|
|
|
static void exec_man_man(const char *path, const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
if (!path)
|
|
|
|
path = "man";
|
2010-07-24 23:20:23 +08:00
|
|
|
execlp(path, "man", page, (char *)NULL);
|
2016-05-08 17:47:27 +08:00
|
|
|
warning_errno(_("failed to exec '%s'"), path);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void exec_man_cmd(const char *cmd, const char *page)
|
|
|
|
{
|
|
|
|
struct strbuf shell_cmd = STRBUF_INIT;
|
|
|
|
strbuf_addf(&shell_cmd, "%s %s", cmd, page);
|
2015-03-08 13:08:00 +08:00
|
|
|
execl(SHELL_PATH, SHELL_PATH, "-c", shell_cmd.buf, (char *)NULL);
|
2016-05-08 17:47:27 +08:00
|
|
|
warning(_("failed to exec '%s'"), cmd);
|
2017-08-31 01:49:45 +08:00
|
|
|
strbuf_release(&shell_cmd);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void add_man_viewer(const char *name)
|
|
|
|
{
|
|
|
|
struct man_viewer_list **p = &man_viewer_list;
|
|
|
|
|
|
|
|
while (*p)
|
|
|
|
p = &((*p)->next);
|
2016-02-23 06:44:32 +08:00
|
|
|
FLEX_ALLOC_STR(*p, name, name);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static int supported_man_viewer(const char *name, size_t len)
|
|
|
|
{
|
|
|
|
return (!strncasecmp("man", name, len) ||
|
|
|
|
!strncasecmp("woman", name, len) ||
|
|
|
|
!strncasecmp("konqueror", name, len));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void do_add_man_viewer_info(const char *name,
|
|
|
|
size_t len,
|
|
|
|
const char *value)
|
|
|
|
{
|
2018-02-15 02:59:32 +08:00
|
|
|
struct man_viewer_info_list *new_man_viewer;
|
|
|
|
FLEX_ALLOC_MEM(new_man_viewer, name, name, len);
|
|
|
|
new_man_viewer->info = xstrdup(value);
|
|
|
|
new_man_viewer->next = man_viewer_info_list;
|
|
|
|
man_viewer_info_list = new_man_viewer;
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static int add_man_viewer_path(const char *name,
|
|
|
|
size_t len,
|
|
|
|
const char *value)
|
|
|
|
{
|
|
|
|
if (supported_man_viewer(name, len))
|
|
|
|
do_add_man_viewer_info(name, len, value);
|
|
|
|
else
|
2012-04-23 20:30:24 +08:00
|
|
|
warning(_("'%s': path for unsupported man viewer.\n"
|
|
|
|
"Please consider using 'man.<tool>.cmd' instead."),
|
2008-08-02 16:08:38 +08:00
|
|
|
name);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int add_man_viewer_cmd(const char *name,
|
|
|
|
size_t len,
|
|
|
|
const char *value)
|
|
|
|
{
|
|
|
|
if (supported_man_viewer(name, len))
|
2012-04-23 20:30:24 +08:00
|
|
|
warning(_("'%s': cmd for supported man viewer.\n"
|
|
|
|
"Please consider using 'man.<tool>.path' instead."),
|
2008-08-02 16:08:38 +08:00
|
|
|
name);
|
|
|
|
else
|
|
|
|
do_add_man_viewer_info(name, len, value);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int add_man_viewer_info(const char *var, const char *value)
|
|
|
|
{
|
2013-01-23 14:27:09 +08:00
|
|
|
const char *name, *subkey;
|
2020-04-11 03:44:28 +08:00
|
|
|
size_t namelen;
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2013-01-23 14:27:09 +08:00
|
|
|
if (parse_config_key(var, "man", &name, &namelen, &subkey) < 0 || !name)
|
2009-04-23 21:49:06 +08:00
|
|
|
return 0;
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2013-01-23 14:27:09 +08:00
|
|
|
if (!strcmp(subkey, "path")) {
|
2008-08-02 16:08:38 +08:00
|
|
|
if (!value)
|
|
|
|
return config_error_nonbool(var);
|
2013-01-23 14:27:09 +08:00
|
|
|
return add_man_viewer_path(name, namelen, value);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
2013-01-23 14:27:09 +08:00
|
|
|
if (!strcmp(subkey, "cmd")) {
|
2008-08-02 16:08:38 +08:00
|
|
|
if (!value)
|
|
|
|
return config_error_nonbool(var);
|
2013-01-23 14:27:09 +08:00
|
|
|
return add_man_viewer_cmd(name, namelen, value);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
config: add ctx arg to config_fn_t
Add a new "const struct config_context *ctx" arg to config_fn_t to hold
additional information about the config iteration operation.
config_context has a "struct key_value_info kvi" member that holds
metadata about the config source being read (e.g. what kind of config
source it is, the filename, etc). In this series, we're only interested
in .kvi, so we could have just used "struct key_value_info" as an arg,
but config_context makes it possible to add/adjust members in the future
without changing the config_fn_t signature. We could also consider other
ways of organizing the args (e.g. moving the config name and value into
config_context or key_value_info), but in my experiments, the
incremental benefit doesn't justify the added complexity (e.g. a
config_fn_t will sometimes invoke another config_fn_t but with a
different config value).
In subsequent commits, the .kvi member will replace the global "struct
config_reader" in config.c, making config iteration a global-free
operation. It requires much more work for the machinery to provide
meaningful values of .kvi, so for now, merely change the signature and
call sites, pass NULL as a placeholder value, and don't rely on the arg
in any meaningful way.
Most of the changes are performed by
contrib/coccinelle/config_fn_ctx.pending.cocci, which, for every
config_fn_t:
- Modifies the signature to accept "const struct config_context *ctx"
- Passes "ctx" to any inner config_fn_t, if needed
- Adds UNUSED attributes to "ctx", if needed
Most config_fn_t instances are easily identified by seeing if they are
called by the various config functions. Most of the remaining ones are
manually named in the .cocci patch. Manual cleanups are still needed,
but the majority of it is trivial; it's either adjusting config_fn_t
that the .cocci patch didn't catch, or adding forward declarations of
"struct config_context ctx" to make the signatures make sense.
The non-trivial changes are in cases where we are invoking a config_fn_t
outside of config machinery, and we now need to decide what value of
"ctx" to pass. These cases are:
- trace2/tr2_cfg.c:tr2_cfg_set_fl()
This is indirectly called by git_config_set() so that the trace2
machinery can notice the new config values and update its settings
using the tr2 config parsing function, i.e. tr2_cfg_cb().
- builtin/checkout.c:checkout_main()
This calls git_xmerge_config() as a shorthand for parsing a CLI arg.
This might be worth refactoring away in the future, since
git_xmerge_config() can call git_default_config(), which can do much
more than just parsing.
Handle them by creating a KVI_INIT macro that initializes "struct
key_value_info" to a reasonable default, and use that to construct the
"ctx" arg.
Signed-off-by: Glen Choo <chooglen@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-29 03:26:22 +08:00
|
|
|
static int git_help_config(const char *var, const char *value,
|
|
|
|
const struct config_context *ctx, void *cb)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
if (!strcmp(var, "help.format")) {
|
|
|
|
if (!value)
|
|
|
|
return config_error_nonbool(var);
|
|
|
|
help_format = parse_help_format(value);
|
|
|
|
return 0;
|
|
|
|
}
|
2012-06-28 14:58:02 +08:00
|
|
|
if (!strcmp(var, "help.htmlpath")) {
|
|
|
|
if (!value)
|
|
|
|
return config_error_nonbool(var);
|
|
|
|
html_path = xstrdup(value);
|
|
|
|
return 0;
|
|
|
|
}
|
2008-08-02 16:08:38 +08:00
|
|
|
if (!strcmp(var, "man.viewer")) {
|
|
|
|
if (!value)
|
|
|
|
return config_error_nonbool(var);
|
|
|
|
add_man_viewer(value);
|
|
|
|
return 0;
|
|
|
|
}
|
2013-12-01 04:55:40 +08:00
|
|
|
if (starts_with(var, "man."))
|
2008-08-02 16:08:38 +08:00
|
|
|
return add_man_viewer_info(var, value);
|
|
|
|
|
config: add ctx arg to config_fn_t
Add a new "const struct config_context *ctx" arg to config_fn_t to hold
additional information about the config iteration operation.
config_context has a "struct key_value_info kvi" member that holds
metadata about the config source being read (e.g. what kind of config
source it is, the filename, etc). In this series, we're only interested
in .kvi, so we could have just used "struct key_value_info" as an arg,
but config_context makes it possible to add/adjust members in the future
without changing the config_fn_t signature. We could also consider other
ways of organizing the args (e.g. moving the config name and value into
config_context or key_value_info), but in my experiments, the
incremental benefit doesn't justify the added complexity (e.g. a
config_fn_t will sometimes invoke another config_fn_t but with a
different config value).
In subsequent commits, the .kvi member will replace the global "struct
config_reader" in config.c, making config iteration a global-free
operation. It requires much more work for the machinery to provide
meaningful values of .kvi, so for now, merely change the signature and
call sites, pass NULL as a placeholder value, and don't rely on the arg
in any meaningful way.
Most of the changes are performed by
contrib/coccinelle/config_fn_ctx.pending.cocci, which, for every
config_fn_t:
- Modifies the signature to accept "const struct config_context *ctx"
- Passes "ctx" to any inner config_fn_t, if needed
- Adds UNUSED attributes to "ctx", if needed
Most config_fn_t instances are easily identified by seeing if they are
called by the various config functions. Most of the remaining ones are
manually named in the .cocci patch. Manual cleanups are still needed,
but the majority of it is trivial; it's either adjusting config_fn_t
that the .cocci patch didn't catch, or adding forward declarations of
"struct config_context ctx" to make the signatures make sense.
The non-trivial changes are in cases where we are invoking a config_fn_t
outside of config machinery, and we now need to decide what value of
"ctx" to pass. These cases are:
- trace2/tr2_cfg.c:tr2_cfg_set_fl()
This is indirectly called by git_config_set() so that the trace2
machinery can notice the new config values and update its settings
using the tr2 config parsing function, i.e. tr2_cfg_cb().
- builtin/checkout.c:checkout_main()
This calls git_xmerge_config() as a shorthand for parsing a CLI arg.
This might be worth refactoring away in the future, since
git_xmerge_config() can call git_default_config(), which can do much
more than just parsing.
Handle them by creating a KVI_INIT macro that initializes "struct
key_value_info" to a reasonable default, and use that to construct the
"ctx" arg.
Signed-off-by: Glen Choo <chooglen@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2023-06-29 03:26:22 +08:00
|
|
|
return git_default_config(var, value, ctx, cb);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
2008-08-29 01:17:46 +08:00
|
|
|
static struct cmdnames main_cmds, other_cmds;
|
2008-08-02 16:08:38 +08:00
|
|
|
|
|
|
|
static int is_git_command(const char *s)
|
|
|
|
{
|
2014-01-03 00:17:11 +08:00
|
|
|
if (is_builtin(s))
|
|
|
|
return 1;
|
|
|
|
|
2014-01-03 00:16:30 +08:00
|
|
|
load_command_list("git-", &main_cmds, &other_cmds);
|
2008-08-02 16:08:38 +08:00
|
|
|
return is_in_cmdlist(&main_cmds, s) ||
|
|
|
|
is_in_cmdlist(&other_cmds, s);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const char *cmd_to_page(const char *git_cmd)
|
|
|
|
{
|
|
|
|
if (!git_cmd)
|
|
|
|
return "git";
|
2013-12-01 04:55:40 +08:00
|
|
|
else if (starts_with(git_cmd, "git"))
|
2008-08-02 16:08:38 +08:00
|
|
|
return git_cmd;
|
|
|
|
else if (is_git_command(git_cmd))
|
2015-09-25 05:07:14 +08:00
|
|
|
return xstrfmt("git-%s", git_cmd);
|
2022-09-02 23:56:44 +08:00
|
|
|
else if (!strcmp("scalar", git_cmd))
|
|
|
|
return xstrdup(git_cmd);
|
2008-08-02 16:08:38 +08:00
|
|
|
else
|
2015-09-25 05:07:14 +08:00
|
|
|
return xstrfmt("git%s", git_cmd);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void setup_man_path(void)
|
|
|
|
{
|
2008-10-10 03:12:12 +08:00
|
|
|
struct strbuf new_path = STRBUF_INIT;
|
2008-08-02 16:08:38 +08:00
|
|
|
const char *old_path = getenv("MANPATH");
|
2014-11-25 03:33:54 +08:00
|
|
|
char *git_man_path = system_path(GIT_MAN_PATH);
|
2008-08-02 16:08:38 +08:00
|
|
|
|
|
|
|
/* We should always put ':' after our path. If there is no
|
|
|
|
* old_path, the ':' at the end will let 'man' to try
|
|
|
|
* system-wide paths after ours to find the manual page. If
|
|
|
|
* there is old_path, we need ':' as delimiter. */
|
2014-11-25 03:33:54 +08:00
|
|
|
strbuf_addstr(&new_path, git_man_path);
|
2008-08-02 16:08:38 +08:00
|
|
|
strbuf_addch(&new_path, ':');
|
|
|
|
if (old_path)
|
|
|
|
strbuf_addstr(&new_path, old_path);
|
|
|
|
|
2014-11-25 03:33:54 +08:00
|
|
|
free(git_man_path);
|
2008-08-02 16:08:38 +08:00
|
|
|
setenv("MANPATH", new_path.buf, 1);
|
|
|
|
|
|
|
|
strbuf_release(&new_path);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void exec_viewer(const char *name, const char *page)
|
|
|
|
{
|
|
|
|
const char *info = get_man_viewer_info(name);
|
|
|
|
|
|
|
|
if (!strcasecmp(name, "man"))
|
|
|
|
exec_man_man(info, page);
|
|
|
|
else if (!strcasecmp(name, "woman"))
|
|
|
|
exec_woman_emacs(info, page);
|
|
|
|
else if (!strcasecmp(name, "konqueror"))
|
|
|
|
exec_man_konqueror(info, page);
|
|
|
|
else if (info)
|
|
|
|
exec_man_cmd(info, page);
|
|
|
|
else
|
2012-04-23 20:30:24 +08:00
|
|
|
warning(_("'%s': unknown man viewer."), name);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
2021-07-04 23:39:12 +08:00
|
|
|
static void show_man_page(const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
struct man_viewer_list *viewer;
|
2008-08-29 23:00:43 +08:00
|
|
|
const char *fallback = getenv("GIT_MAN_VIEWER");
|
2008-08-02 16:08:38 +08:00
|
|
|
|
|
|
|
setup_man_path();
|
|
|
|
for (viewer = man_viewer_list; viewer; viewer = viewer->next)
|
|
|
|
{
|
|
|
|
exec_viewer(viewer->name, page); /* will return when unable */
|
|
|
|
}
|
2008-08-29 23:00:43 +08:00
|
|
|
if (fallback)
|
|
|
|
exec_viewer(fallback, page);
|
2008-08-02 16:08:38 +08:00
|
|
|
exec_viewer("man", page);
|
2012-04-23 20:30:24 +08:00
|
|
|
die(_("no man viewer handled the request"));
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
2021-07-04 23:39:12 +08:00
|
|
|
static void show_info_page(const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
2009-01-18 20:00:09 +08:00
|
|
|
setenv("INFOPATH", system_path(GIT_INFO_PATH), 1);
|
2010-07-24 23:20:23 +08:00
|
|
|
execlp("info", "info", "gitman", page, (char *)NULL);
|
2012-04-23 20:30:24 +08:00
|
|
|
die(_("no info viewer handled the request"));
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void get_html_page_path(struct strbuf *page_path, const char *page)
|
|
|
|
{
|
|
|
|
struct stat st;
|
2014-11-25 03:33:54 +08:00
|
|
|
char *to_free = NULL;
|
|
|
|
|
2012-06-28 14:58:02 +08:00
|
|
|
if (!html_path)
|
2014-11-25 03:33:54 +08:00
|
|
|
html_path = to_free = system_path(GIT_HTML_PATH);
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2021-09-14 21:27:17 +08:00
|
|
|
/*
|
|
|
|
* Check that the page we're looking for exists.
|
|
|
|
*/
|
2012-06-28 14:58:03 +08:00
|
|
|
if (!strstr(html_path, "://")) {
|
2021-09-14 21:27:17 +08:00
|
|
|
if (stat(mkpath("%s/%s.html", html_path, page), &st)
|
2012-06-28 14:58:03 +08:00
|
|
|
|| !S_ISREG(st.st_mode))
|
2021-09-14 21:27:17 +08:00
|
|
|
die("'%s/%s.html': documentation file not found.",
|
|
|
|
html_path, page);
|
2012-06-28 14:58:03 +08:00
|
|
|
}
|
2008-08-02 16:08:38 +08:00
|
|
|
|
|
|
|
strbuf_init(page_path, 0);
|
|
|
|
strbuf_addf(page_path, "%s/%s.html", html_path, page);
|
2014-11-25 03:33:54 +08:00
|
|
|
free(to_free);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
2009-06-19 01:28:43 +08:00
|
|
|
static void open_html(const char *path)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
2010-07-24 23:20:23 +08:00
|
|
|
execl_git_cmd("web--browse", "-c", "help.browser", path, (char *)NULL);
|
2008-08-02 16:08:38 +08:00
|
|
|
}
|
|
|
|
|
2021-07-04 23:39:12 +08:00
|
|
|
static void show_html_page(const char *page)
|
2008-08-02 16:08:38 +08:00
|
|
|
{
|
|
|
|
struct strbuf page_path; /* it leaks but we exec bellow */
|
|
|
|
|
|
|
|
get_html_page_path(&page_path, page);
|
|
|
|
|
|
|
|
open_html(page_path.buf);
|
|
|
|
}
|
|
|
|
|
2016-08-27 01:58:35 +08:00
|
|
|
static const char *check_git_cmd(const char* cmd)
|
|
|
|
{
|
|
|
|
char *alias;
|
|
|
|
|
|
|
|
if (is_git_command(cmd))
|
|
|
|
return cmd;
|
|
|
|
|
|
|
|
alias = alias_lookup(cmd);
|
|
|
|
if (alias) {
|
2018-10-09 19:59:07 +08:00
|
|
|
const char **argv;
|
|
|
|
int count;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* handle_builtin() in git.c rewrites "git cmd --help"
|
|
|
|
* to "git help --exclude-guides cmd", so we can use
|
|
|
|
* exclude_guides to distinguish "git cmd --help" from
|
|
|
|
* "git help cmd". In the latter case, or if cmd is an
|
|
|
|
* alias for a shell command, just print the alias
|
|
|
|
* definition.
|
|
|
|
*/
|
|
|
|
if (!exclude_guides || alias[0] == '!') {
|
|
|
|
printf_ln(_("'%s' is aliased to '%s'"), cmd, alias);
|
|
|
|
free(alias);
|
|
|
|
exit(0);
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* Otherwise, we pretend that the command was "git
|
|
|
|
* word0 --help". We use split_cmdline() to get the
|
|
|
|
* first word of the alias, to ensure that we use the
|
|
|
|
* same rules as when the alias is actually
|
|
|
|
* used. split_cmdline() modifies alias in-place.
|
|
|
|
*/
|
|
|
|
fprintf_ln(stderr, _("'%s' is aliased to '%s'"), cmd, alias);
|
|
|
|
count = split_cmdline(alias, &argv);
|
|
|
|
if (count < 0)
|
|
|
|
die(_("bad alias.%s string: %s"), cmd,
|
|
|
|
split_cmdline_strerror(count));
|
|
|
|
free(argv);
|
|
|
|
UNLEAK(alias);
|
|
|
|
return alias;
|
2016-08-27 01:58:35 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
if (exclude_guides)
|
|
|
|
return help_unknown_cmd(cmd);
|
|
|
|
|
|
|
|
return cmd;
|
|
|
|
}
|
|
|
|
|
2022-02-22 03:38:50 +08:00
|
|
|
static void no_help_format(const char *opt_mode, enum help_format fmt)
|
|
|
|
{
|
|
|
|
const char *opt_fmt;
|
|
|
|
|
|
|
|
switch (fmt) {
|
|
|
|
case HELP_FORMAT_NONE:
|
|
|
|
return;
|
|
|
|
case HELP_FORMAT_MAN:
|
|
|
|
opt_fmt = "--man";
|
|
|
|
break;
|
|
|
|
case HELP_FORMAT_INFO:
|
|
|
|
opt_fmt = "--info";
|
|
|
|
break;
|
|
|
|
case HELP_FORMAT_WEB:
|
|
|
|
opt_fmt = "--web";
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
BUG("unreachable");
|
|
|
|
}
|
|
|
|
|
|
|
|
usage_msg_optf(_("options '%s' and '%s' cannot be used together"),
|
|
|
|
builtin_help_usage, builtin_help_options, opt_mode,
|
|
|
|
opt_fmt);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void opt_mode_usage(int argc, const char *opt_mode,
|
|
|
|
enum help_format fmt)
|
2021-09-22 06:40:36 +08:00
|
|
|
{
|
|
|
|
if (argc)
|
2022-02-22 03:38:48 +08:00
|
|
|
usage_msg_optf(_("the '%s' option doesn't take any non-option arguments"),
|
|
|
|
builtin_help_usage, builtin_help_options,
|
|
|
|
opt_mode);
|
2022-02-22 03:38:50 +08:00
|
|
|
|
|
|
|
no_help_format(opt_mode, fmt);
|
2021-09-22 06:40:36 +08:00
|
|
|
}
|
|
|
|
|
2008-08-02 16:08:38 +08:00
|
|
|
int cmd_help(int argc, const char **argv, const char *prefix)
|
|
|
|
{
|
|
|
|
int nongit;
|
2010-01-09 13:10:05 +08:00
|
|
|
enum help_format parsed_help_format;
|
2021-07-04 23:39:12 +08:00
|
|
|
const char *page;
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2009-05-24 02:53:12 +08:00
|
|
|
argc = parse_options(argc, argv, prefix, builtin_help_options,
|
2008-08-02 16:08:38 +08:00
|
|
|
builtin_help_usage, 0);
|
2010-01-09 13:10:05 +08:00
|
|
|
parsed_help_format = help_format;
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2022-02-22 03:38:51 +08:00
|
|
|
if (cmd_mode != HELP_ACTION_ALL &&
|
|
|
|
(show_external_commands >= 0 ||
|
|
|
|
show_aliases >= 0))
|
|
|
|
usage_msg_opt(_("the '--no-[external-commands|aliases]' options can only be used with '--all'"),
|
|
|
|
builtin_help_usage, builtin_help_options);
|
|
|
|
|
2021-09-22 06:40:36 +08:00
|
|
|
switch (cmd_mode) {
|
|
|
|
case HELP_ACTION_ALL:
|
2022-02-22 03:38:50 +08:00
|
|
|
opt_mode_usage(argc, "--all", help_format);
|
2018-05-21 02:40:01 +08:00
|
|
|
if (verbose) {
|
|
|
|
setup_pager();
|
2022-02-22 03:38:51 +08:00
|
|
|
list_all_cmds_help(show_external_commands,
|
|
|
|
show_aliases);
|
2018-05-21 02:40:01 +08:00
|
|
|
return 0;
|
|
|
|
}
|
2012-04-23 20:30:24 +08:00
|
|
|
printf(_("usage: %s%s"), _(git_usage_string), "\n\n");
|
2014-01-03 00:16:30 +08:00
|
|
|
load_command_list("git-", &main_cmds, &other_cmds);
|
2021-09-22 06:40:39 +08:00
|
|
|
list_commands(&main_cmds, &other_cmds);
|
2021-09-22 06:40:36 +08:00
|
|
|
printf("%s\n", _(git_more_info_string));
|
|
|
|
break;
|
|
|
|
case HELP_ACTION_GUIDES:
|
2022-02-22 03:38:50 +08:00
|
|
|
opt_mode_usage(argc, "--guides", help_format);
|
2020-08-05 09:19:05 +08:00
|
|
|
list_guides_help();
|
2012-04-23 20:30:24 +08:00
|
|
|
printf("%s\n", _(git_more_info_string));
|
2021-09-22 06:40:34 +08:00
|
|
|
return 0;
|
2021-09-22 06:40:36 +08:00
|
|
|
case HELP_ACTION_CONFIG_FOR_COMPLETION:
|
2022-02-22 03:38:50 +08:00
|
|
|
opt_mode_usage(argc, "--config-for-completion", help_format);
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
list_config_help(SHOW_CONFIG_VARS);
|
|
|
|
return 0;
|
2022-08-05 00:28:33 +08:00
|
|
|
case HELP_ACTION_USER_INTERFACES:
|
|
|
|
opt_mode_usage(argc, "--user-interfaces", help_format);
|
|
|
|
list_user_interfaces_help();
|
|
|
|
return 0;
|
2022-08-05 00:28:34 +08:00
|
|
|
case HELP_ACTION_DEVELOPER_INTERFACES:
|
|
|
|
opt_mode_usage(argc, "--developer-interfaces", help_format);
|
|
|
|
list_developer_interfaces_help();
|
|
|
|
return 0;
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
case HELP_ACTION_CONFIG_SECTIONS_FOR_COMPLETION:
|
2022-02-22 03:38:50 +08:00
|
|
|
opt_mode_usage(argc, "--config-sections-for-completion",
|
|
|
|
help_format);
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
list_config_help(SHOW_CONFIG_SECTIONS);
|
2021-09-22 06:40:36 +08:00
|
|
|
return 0;
|
|
|
|
case HELP_ACTION_CONFIG:
|
2022-02-22 03:38:50 +08:00
|
|
|
opt_mode_usage(argc, "--config", help_format);
|
2018-05-26 21:55:24 +08:00
|
|
|
setup_pager();
|
help / completion: make "git help" do the hard work
The "help" builtin has been able to emit configuration variables since
e17ca926371 (completion: drop the hard coded list of config vars,
2018-05-26), but it hasn't produced exactly the format the completion
script wanted. Let's do that.
We got partway there in 2675ea1cc0f (completion: use 'sort -u' to
deduplicate config variable names, 2019-08-13) and
d9438873c4d (completion: deduplicate configuration sections,
2019-08-13), but after both we still needed some sorting,
de-duplicating and awk post-processing of the list.
We can instead simply do the relevant parsing ourselves (we were doing
most of it already), and call string_list_remove_duplicates() after
already sorting the list, so the caller doesn't need to invoke "sort
-u". The "--config-for-completion" output is the same as before after
being passed through "sort -u".
Then add a new "--config-sections-for-completion" option. Under that
output we'll emit config sections like "alias" (instead of "alias." in
the --config-for-completion output).
We need to be careful to leave the "--config-for-completion" option
compatible with users git, but are still running a shell with an older
git-completion.bash. If we e.g. changed the option name they'd see
messages about git-completion.bash being unable to find the
"--config-for-completion" option.
Such backwards compatibility isn't something we should bend over
backwards for, it's only helping users who:
* Upgrade git
* Are in an old shell
* The git-completion.bash in that shell hasn't cached the old
"--config-for-completion" output already.
But since it's easy in this case to retain compatibility, let's do it,
the older versions of git-completion.bash won't care that the input
they get doesn't change after a "sort -u".
While we're at it let's make "--config-for-completion" die if there's
anything left over in "argc", and do the same in the new
"--config-sections-for-completion" option.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-22 06:40:38 +08:00
|
|
|
list_config_help(SHOW_CONFIG_HUMAN);
|
2018-05-26 21:55:24 +08:00
|
|
|
printf("\n%s\n", _("'git help config' for more information"));
|
2008-08-02 16:08:38 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!argv[0]) {
|
2012-04-23 20:30:24 +08:00
|
|
|
printf(_("usage: %s%s"), _(git_usage_string), "\n\n");
|
2008-08-02 16:08:38 +08:00
|
|
|
list_common_cmds_help();
|
2012-04-23 20:30:24 +08:00
|
|
|
printf("\n%s\n", _(git_more_info_string));
|
2008-08-02 16:08:38 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-12-02 03:27:34 +08:00
|
|
|
setup_git_directory_gently(&nongit);
|
|
|
|
git_config(git_help_config, NULL);
|
|
|
|
|
2012-06-22 20:48:46 +08:00
|
|
|
if (parsed_help_format != HELP_FORMAT_NONE)
|
2010-01-09 13:10:05 +08:00
|
|
|
help_format = parsed_help_format;
|
2012-06-22 20:48:46 +08:00
|
|
|
if (help_format == HELP_FORMAT_NONE)
|
|
|
|
help_format = parse_help_format(DEFAULT_HELP_FORMAT);
|
2010-01-09 13:10:05 +08:00
|
|
|
|
2016-08-27 01:58:35 +08:00
|
|
|
argv[0] = check_git_cmd(argv[0]);
|
2008-08-02 16:08:38 +08:00
|
|
|
|
2021-07-04 23:39:12 +08:00
|
|
|
page = cmd_to_page(argv[0]);
|
2008-08-02 16:08:38 +08:00
|
|
|
switch (help_format) {
|
2010-01-09 13:10:05 +08:00
|
|
|
case HELP_FORMAT_NONE:
|
2008-08-02 16:08:38 +08:00
|
|
|
case HELP_FORMAT_MAN:
|
2021-07-04 23:39:12 +08:00
|
|
|
show_man_page(page);
|
2008-08-02 16:08:38 +08:00
|
|
|
break;
|
|
|
|
case HELP_FORMAT_INFO:
|
2021-07-04 23:39:12 +08:00
|
|
|
show_info_page(page);
|
2008-08-02 16:08:38 +08:00
|
|
|
break;
|
|
|
|
case HELP_FORMAT_WEB:
|
2021-07-04 23:39:12 +08:00
|
|
|
show_html_page(page);
|
2008-08-02 16:08:38 +08:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|