From: Duy Nguyen <pclouds@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 15/15] for-each-ref: use get_pretty_userformat in --pretty
Date: Tue, 4 Jun 2013 19:57:54 +0700 [thread overview]
Message-ID: <CACsJy8ABNVW=KT9mR4oqiXisEwb5Q3ri4zM467dB-N5ELn=FYQ@mail.gmail.com> (raw)
In-Reply-To: <1370349337-20938-16-git-send-email-artagnon@gmail.com>
On Tue, Jun 4, 2013 at 7:35 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
> Use get_pretty_userformat() to interpret the --pretty string. This
> means that leading you can now reference a format specified in a pretty.*
> configuration variable as an argument to 'git for-each-ref --pretty='.
> There are two caveats:
>
> 1. A leading "format:" or "tformat:" is automatically stripped and
> ignored. Separator semantics are not configurable (yet).
>
> 2. No built-in formats are available. The ones specified in
> pretty-formats (oneline, short etc) don't make sense when displaying
> refs anyway.
>
I spoke too early about the concern with this patch. At first it
looked like you replace default formats with config keys. But nope,
this is brilliant.
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
> Documentation/git-for-each-ref.txt | 3 +++
> builtin/for-each-ref.c | 16 +++++++++-------
> 2 files changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
> index 05ff7ba..7f3cba5 100644
> --- a/Documentation/git-for-each-ref.txt
> +++ b/Documentation/git-for-each-ref.txt
> @@ -60,6 +60,9 @@ calculated.
> +
> Caveats:
>
> +0. No built-in formats from PRETTY FORMATS (like oneline, short) are
> + available.
> +
> 1. Many of the placeholders in "PRETTY FORMATS" are designed to work
> specifically on commit objects: when non-commit objects are
> supplied, those placeholders won't work.
> diff --git a/builtin/for-each-ref.c b/builtin/for-each-ref.c
> index edaa6b2..c00ab05 100644
> --- a/builtin/for-each-ref.c
> +++ b/builtin/for-each-ref.c
> @@ -1146,7 +1146,7 @@ int cmd_for_each_ref(int argc, const char **argv, const char *prefix)
> int num_refs;
> const char *default_format = "%(objectname) %(objecttype)\t%(refname)";
> const char *format = default_format;
> - const char *pretty = NULL;
> + const char *pretty_raw = NULL, *pretty_userformat = NULL;
> struct ref_sort *sort = NULL, **sort_tail = &sort;
> int maxcount = 0, quote_style = 0;
> struct refinfo **refs;
> @@ -1165,13 +1165,15 @@ int cmd_for_each_ref(int argc, const char **argv, const char *prefix)
> OPT_GROUP(""),
> OPT_INTEGER( 0 , "count", &maxcount, N_("show only <n> matched refs")),
> OPT_STRING( 0 , "format", &format, N_("format"), N_("format to use for the output")),
> - OPT_STRING( 0 , "pretty", &pretty, N_("format"), N_("alternative format to use for the output")),
> + OPT_STRING( 0 , "pretty", &pretty_raw, N_("format"), N_("alternative format to use for the output")),
> OPT_CALLBACK(0 , "sort", sort_tail, N_("key"),
> N_("field name to sort on"), &opt_parse_sort),
> OPT_END(),
> };
>
> parse_options(argc, argv, prefix, opts, for_each_ref_usage, 0);
> + if (pretty_raw)
> + pretty_userformat = get_pretty_userformat(pretty_raw);
> if (maxcount < 0) {
> error("invalid --count argument: `%d'", maxcount);
> usage_with_options(for_each_ref_usage, opts);
> @@ -1180,10 +1182,10 @@ int cmd_for_each_ref(int argc, const char **argv, const char *prefix)
> error("more than one quoting style?");
> usage_with_options(for_each_ref_usage, opts);
> }
> - if (format != default_format && pretty)
> + if (format != default_format && pretty_userformat)
> die("--format and --pretty cannot be used together");
> - if ((pretty && verify_format(pretty, 1)) ||
> - (!pretty && verify_format(format, 0)))
> + if ((pretty_userformat && verify_format(pretty_userformat, 1)) ||
> + (!pretty_userformat && verify_format(format, 0)))
> usage_with_options(for_each_ref_usage, opts);
>
> if (!sort)
> @@ -1204,8 +1206,8 @@ int cmd_for_each_ref(int argc, const char **argv, const char *prefix)
> if (!maxcount || num_refs < maxcount)
> maxcount = num_refs;
>
> - if (pretty)
> - show_pretty_refs(refs, maxcount, pretty, quote_style);
> + if (pretty_userformat)
> + show_pretty_refs(refs, maxcount, pretty_userformat, quote_style);
> else
> show_refs(refs, maxcount, format, quote_style);
> return 0;
> --
> 1.8.3.GIT
>
--
Duy
next prev parent reply other threads:[~2013-06-04 12:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 12:35 [PATCH 00/15] Towards a more awesome git-branch Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 01/15] for-each-ref, quote: convert *_quote_print -> *_quote_buf Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 02/15] for-each-ref: don't print out elements directly Ramkumar Ramachandra
2013-06-04 23:13 ` Junio C Hamano
2013-06-04 23:44 ` Duy Nguyen
2013-06-04 12:35 ` [PATCH 03/15] tar-tree: remove dependency on sq_quote_print() Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 04/15] quote: remove sq_quote_print() Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 05/15] pretty: extend pretty_print_context with callback Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 06/15] pretty: limit recursion in format_commit_one() Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 07/15] pretty: allow passing NULL commit to format_commit_message() Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 08/15] for-each-ref: get --pretty using format_commit_message Ramkumar Ramachandra
2013-06-04 21:12 ` Eric Sunshine
2013-06-05 13:21 ` Duy Nguyen
2013-06-05 17:09 ` Junio C Hamano
2013-06-06 0:07 ` Duy Nguyen
2013-06-04 12:35 ` [PATCH 09/15] for-each-ref: teach verify_format() about pretty's syntax Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 10/15] for-each-ref: introduce format specifier %>(*) and %<(*) Ramkumar Ramachandra
2013-06-04 12:54 ` Duy Nguyen
2013-06-05 8:14 ` Ramkumar Ramachandra
2013-06-05 10:15 ` Duy Nguyen
2013-06-04 12:35 ` [PATCH 11/15] for-each-ref: introduce %(HEAD) marker Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 12/15] for-each-ref: introduce %(upstream:track[short]) Ramkumar Ramachandra
2013-06-04 21:14 ` Eric Sunshine
2013-06-04 12:35 ` [PATCH 13/15] for-each-ref: improve responsiveness of %(upstream:track) Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 14/15] pretty: introduce get_pretty_userformat Ramkumar Ramachandra
2013-06-04 12:35 ` [PATCH 15/15] for-each-ref: use get_pretty_userformat in --pretty Ramkumar Ramachandra
2013-06-04 12:57 ` Duy Nguyen [this message]
2013-06-04 21:15 ` Eric Sunshine
2013-06-04 12:49 ` [PATCH 00/15] Towards a more awesome git-branch Duy Nguyen
2013-06-05 8:11 ` Ramkumar Ramachandra
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 10:32 [RESEND][PATCH 00/15] Towards a more awesome git branch Ramkumar Ramachandra
2013-07-09 10:32 ` [PATCH 15/15] for-each-ref: use get_pretty_userformat in --pretty Ramkumar Ramachandra
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8ABNVW=KT9mR4oqiXisEwb5Q3ri4zM467dB-N5ELn=FYQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=artagnon@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).