From: Stephen Boyd <bebarino@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 2/3] parse-options: add PARSE_OPT_CUSTOM_ARGH for complicated argh's
Date: Sun, 17 May 2009 03:47:03 -0700 [thread overview]
Message-ID: <1242557224-8411-2-git-send-email-bebarino@gmail.com> (raw)
In-Reply-To: <1242557224-8411-1-git-send-email-bebarino@gmail.com>
If argh is complicated, i.e. the option takes more than one argument,
don't add the brackets around argh in the usage message.
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
---
This is used in the next patch to for --reflog[=<n>[,<base>]]
Maybe someone can think of a better name?
parse-options.c | 26 +++++++++++++++++---------
parse-options.h | 4 ++++
2 files changed, 21 insertions(+), 9 deletions(-)
diff --git a/parse-options.c b/parse-options.c
index cf71bcf..cd9ab4f 100644
--- a/parse-options.c
+++ b/parse-options.c
@@ -361,6 +361,20 @@ int parse_options(int argc, const char **argv, const struct option *options,
return parse_options_end(&ctx);
}
+static int usage_argh(const struct option *opts, int pos)
+{
+ const char *s;
+ int custom = opts->flags & PARSE_OPT_CUSTOM_ARGH;
+ if (opts->flags & PARSE_OPT_OPTARG)
+ if (opts->long_name)
+ s = custom ? "[=%s]" : "[=<%s>]";
+ else
+ s = custom ? "[%s]" : "[<%s>]";
+ else
+ s = custom ? " %s" : " <%s>";
+ return pos + fprintf(stderr, s, opts->argh);
+}
+
#define USAGE_OPTS_WIDTH 24
#define USAGE_GAP 2
@@ -421,15 +435,9 @@ int usage_with_options_internal(const char * const *usagestr,
break;
/* FALLTHROUGH */
case OPTION_STRING:
- if (opts->argh) {
- if (opts->flags & PARSE_OPT_OPTARG)
- if (opts->long_name)
- pos += fprintf(stderr, "[=<%s>]", opts->argh);
- else
- pos += fprintf(stderr, "[<%s>]", opts->argh);
- else
- pos += fprintf(stderr, " <%s>", opts->argh);
- } else {
+ if (opts->argh)
+ pos += usage_argh(opts, pos);
+ else {
if (opts->flags & PARSE_OPT_OPTARG)
if (opts->long_name)
pos += fprintf(stderr, "[=...]");
diff --git a/parse-options.h b/parse-options.h
index b54eec1..671a635 100644
--- a/parse-options.h
+++ b/parse-options.h
@@ -31,6 +31,7 @@ enum parse_opt_option_flags {
PARSE_OPT_NONEG = 4,
PARSE_OPT_HIDDEN = 8,
PARSE_OPT_LASTARG_DEFAULT = 16,
+ PARSE_OPT_CUSTOM_ARGH = 64,
};
struct option;
@@ -66,6 +67,9 @@ typedef int parse_opt_cb(const struct option *, const char *arg, int unset);
* PARSE_OPT_NONEG: says that this option cannot be negated
* PARSE_OPT_HIDDEN this option is skipped in the default usage, showed in
* the long one.
+ * PARSE_OPT_CUSTOM_ARGH: says that argh shouldn't be enclosed in brackets
+ * (i.e. '<argh>') in the help message.
+ * Useful for options with multiple parameters.
*
* `callback`::
* pointer to the callback to use for OPTION_CALLBACK.
--
1.6.3.1.30.g55524
next prev parent reply other threads:[~2009-05-17 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 10:47 [PATCH 1/3] show-branch: Fix die message in parse_reflog_param() Stephen Boyd
2009-05-17 10:47 ` Stephen Boyd [this message]
2009-05-17 10:47 ` [PATCH 3/3] show-branch: migrate to parse-options API Stephen Boyd
2009-05-18 6:14 ` [PATCH 2/3] parse-options: add PARSE_OPT_CUSTOM_ARGH for complicated argh's Junio C Hamano
2009-05-18 7:08 ` Stephen Boyd
2009-05-18 7:57 ` Junio C Hamano
2009-05-18 8:06 ` Stephen Boyd
2009-05-18 22:52 ` Jakub Narebski
2009-05-19 5:09 ` Sverre Rabbelier
2009-05-21 7:33 ` [PATCHv2 1/2] parse-options: add PARSE_OPT_LITERAL_ARGHELP " Stephen Boyd
2009-05-21 16:26 ` Junio C Hamano
2009-05-21 16:51 ` René Scharfe
2009-05-21 19:03 ` Stephen Boyd
2009-05-21 21:27 ` Stephen Boyd
2009-05-21 7:33 ` [PATCHv2 2/2] show-branch: migrate to parse-options API Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242557224-8411-2-git-send-email-bebarino@gmail.com \
--to=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).