From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 06/15] ref-filter: move need_color_reset_at_eol into ref_format
Date: Thu, 13 Jul 2017 13:36:59 -0700 [thread overview]
Message-ID: <xmqqh8ygul90.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170713150230.sy7zuksbgjcrllxh@sigill.intra.peff.net> (Jeff King's message of "Thu, 13 Jul 2017 11:02:30 -0400")
Jeff King <peff@peff.net> writes:
> Calling verify_ref_format() doesn't just confirm that the
> format is sane; it actually sets some global variables that
> will be used later when formatting the refs. These logically
> should belong to the ref_format, which would make it
> possible to use multiple formats within a single program
> invocation.
>
> Let's move one such flag into the ref_format struct. There
> are still others that would need to be moved before it would
> be safe to use multiple formats, but this commit gives a
> blueprint for how that should look.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> This commit is strictly optional for this series, but I wanted to give a
> sense of how the rest of the movement might look, since I was thinking
> about it. The big thing to move would be the used_atoms array, but I
> punted on that for now.
Heh, when I saw the hunk at 661,+7, used_atom[] was what immediately
came to mind. It is OK to punt for the purpose of this patch, but
moving these statics into the ref-format structure would be a good
move in the longer term.
Thanks.
>
> ref-filter.c | 7 +++----
> ref-filter.h | 3 +++
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/ref-filter.c b/ref-filter.c
> index 66d234bb1..178396e1f 100644
> --- a/ref-filter.c
> +++ b/ref-filter.c
> @@ -97,7 +97,6 @@ static struct used_atom {
> } u;
> } *used_atom;
> static int used_atom_cnt, need_tagged, need_symref;
> -static int need_color_reset_at_eol;
>
> static void color_atom_parser(struct used_atom *atom, const char *color_value)
> {
> @@ -661,7 +660,7 @@ int verify_ref_format(struct ref_format *format)
> {
> const char *cp, *sp;
>
> - need_color_reset_at_eol = 0;
> + format->need_color_reset_at_eol = 0;
> for (cp = format->format; *cp && (sp = find_next(cp)); ) {
> const char *color, *ep = strchr(sp, ')');
> int at;
> @@ -673,7 +672,7 @@ int verify_ref_format(struct ref_format *format)
> cp = ep + 1;
>
> if (skip_prefix(used_atom[at].name, "color:", &color))
> - need_color_reset_at_eol = !!strcmp(color, "reset");
> + format->need_color_reset_at_eol = !!strcmp(color, "reset");
> }
> return 0;
> }
> @@ -2083,7 +2082,7 @@ void format_ref_array_item(struct ref_array_item *info,
> sp = cp + strlen(cp);
> append_literal(cp, sp, &state);
> }
> - if (need_color_reset_at_eol) {
> + if (format->need_color_reset_at_eol) {
> struct atom_value resetv;
> resetv.s = GIT_COLOR_RESET;
> append_atom(&resetv, &state);
> diff --git a/ref-filter.h b/ref-filter.h
> index 2bb58879d..9e1e89c19 100644
> --- a/ref-filter.h
> +++ b/ref-filter.h
> @@ -79,6 +79,9 @@ struct ref_format {
> */
> const char *format;
> int quote_style;
> +
> + /* Internal state to ref-filter */
> + int need_color_reset_at_eol;
> };
>
> #define REF_FORMAT_INIT { NULL, 0 }
next prev parent reply other threads:[~2017-07-13 20:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 14:55 [PATCH 0/15] making user-format colors conditional on config/tty Jeff King
2017-07-13 14:56 ` [PATCH 01/15] check return value of verify_ref_format() Jeff King
2017-07-13 14:56 ` [PATCH 02/15] docs/for-each-ref: update pointer to color syntax Jeff King
2017-07-13 20:15 ` Junio C Hamano
2017-07-13 14:58 ` [PATCH 03/15] t: use test_decode_color rather than literal ANSI codes Jeff King
2017-07-13 18:40 ` Stefan Beller
2017-07-13 18:45 ` Jeff King
2017-07-13 19:27 ` Junio C Hamano
2017-07-14 11:50 ` Jeff King
2017-07-13 20:18 ` Junio C Hamano
2017-07-13 14:58 ` [PATCH 04/15] ref-filter: simplify automatic color reset Jeff King
2017-07-13 15:01 ` [PATCH 05/15] ref-filter: abstract ref format into its own struct Jeff King
2017-07-13 18:51 ` Stefan Beller
2017-07-13 20:34 ` Junio C Hamano
2017-07-13 21:32 ` Junio C Hamano
2017-07-13 22:01 ` Stefan Beller
2017-07-13 22:45 ` Junio C Hamano
2017-07-13 15:02 ` [PATCH 06/15] ref-filter: move need_color_reset_at_eol into ref_format Jeff King
2017-07-13 20:36 ` Junio C Hamano [this message]
2017-07-13 15:02 ` [PATCH 07/15] ref-filter: provide a function for parsing sort options Jeff King
2017-07-13 15:02 ` [PATCH 08/15] ref-filter: make parse_ref_filter_atom a private function Jeff King
2017-07-13 15:02 ` [PATCH 09/15] ref-filter: factor out the parsing of sorting atoms Jeff King
2017-07-13 15:06 ` [PATCH 10/15] ref-filter: pass ref_format struct to atom parsers Jeff King
2017-07-13 15:07 ` [PATCH 11/15] color: check color.ui in git_default_config() Jeff King
2017-07-13 15:07 ` [PATCH 12/15] for-each-ref: load config earlier Jeff King
2017-07-13 15:07 ` [PATCH 13/15] rev-list: pass diffopt->use_colors through to pretty-print Jeff King
2017-07-13 15:08 ` [PATCH 14/15] pretty: respect color settings for %C placeholders Jeff King
2017-07-13 15:09 ` [PATCH 15/15] ref-filter: consult want_color() before emitting colors Jeff King
2017-07-13 19:14 ` [PATCH 0/15] making user-format colors conditional on config/tty Stefan Beller
2017-07-13 20:46 ` Junio C Hamano
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=xmqqh8ygul90.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).