git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v5 02/11] ref-filter: make `color` use `ref_formatting_state`

From
Karthik Nayak <karthik.188@gmail.com>
Date
Jul 27, 2015, 17:16 UTC
Message-ID
<CAOLa=ZQ6tO+n+V=iVZQi0+UOPDQvfGSNjxCyOTZCOFic-1wHaw@mail.gmail.com>
In-Reply-To
<vpqlhe192d5.fsf@anie.imag.fr>

On Mon, Jul 27, 2015 at 6:36 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 44 quoted lines
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> --- a/ref-filter.c
>> +++ b/ref-filter.c
>> @@ -1195,6 +1197,11 @@ void ref_array_sort(struct ref_sorting *sorting, struct ref_array *array)
>>  static void ref_formatting(struct ref_formatting_state *state,
>>                          struct atom_value *v, struct strbuf *value)
>>  {
>> +     if (state->color) {
>> +             strbuf_addstr(value, state->color);
>> +             free(state->color);
>> +             state->color = NULL;
>> +     }
>>       strbuf_addf(value, "%s", v->s);
>>  }
>>
>> @@ -1266,6 +1273,13 @@ static void emit(const char *cp, const char *ep)
>>       }
>>  }
>>
>> +static void apply_pseudo_state(struct ref_formatting_state *state,
>> +                            struct atom_value *v)
>> +{
>> +     if (v->color)
>> +             state->color = (char *)v->s;
>> +}
>> +
>>  void show_ref_array_item(struct ref_array_item *info, const char *format, int quote_style)
>>  {
>>       const char *cp, *sp, *ep;
>
> It's not clear enough in the code and history that these these two
> functions are symmetrical.
>
> You can find better names. 'apply_pseudo_state' seems wrong it two ways:
> it does not _apply_ the state, but it stores it. And it's a "pseudo-atom
> related state", but not a "pseudo-state".
>
> How about
>
> ref_formatting -> apply_formatting_state
> apply_pseudo_state -> store_formatting_state
>
> ?
Yes, your suggested naming scheme is better. Ill adopt this.
Show 11 quoted lines
>
> Actually, I would even call these functions right from
> show_ref_array_item, so that the result look like this:
>
>                 if (atomv->pseudo_atom)
>                         store_formatting_state(&state, atomv);
>                 else {
>                         apply_formatting_state(&state, atomv);
>                         reset_formatting_state(&state);
>                         print_value(&state, atomv);
>                 }

This would eliminate that extra strbuf in print_value() wouldn't it, but this would also mean that we replace the value in atomv to hold the new formatted value. Sounds good to me. Thanks :)

Show 19 quoted lines
>
> In the history, if you are to introduce a dumb version of ref_formatting
> in PATCH 1, I think you should also introduce a dumb (actually, totally
> empty) version of apply_pseudo_state. Then, further patches would just
> add a few lines in each function, and ...
>
>> @@ -1281,7 +1295,10 @@ void show_ref_array_item(struct ref_array_item *info, const char *format, int qu
>>               if (cp < sp)
>>                       emit(cp, sp);
>>               get_ref_atom_value(info, parse_ref_filter_atom(sp + 2, ep), &atomv);
>> -             print_value(&state, atomv);
>> +             if (atomv->pseudo_atom)
>> +                     apply_pseudo_state(&state, atomv);
>> +             else
>> +                     print_value(&state, atomv);
>>       }
>
> ... this hunk would belong to PATCH 1.
>
I'll add a placeholder for this in the PATCH 1. Thanks :D
-- 
Regards,
Karthik Nayak
Previous: Matthieu MoyNext: Karthik Nayak
Message 9 of 38 in “port tag.c to use ref-filter APIs”
  1. 00/11 port tag.c to use ref-filter APIsKarthik Nayak, Jul 27, 2015
  2. 01/11 ref-filter: introduce 'ref_formatting_state'Karthik Nayak, Jul 27, 2015
  3. 02/11 ref-filter: make `color` use `ref_formatting_state`Karthik Nayak, Jul 27, 2015
  4. Matthieu MoyJul 27, 2015
  5. Junio C HamanoJul 27, 2015
  6. Karthik NayakJul 27, 2015
  7. Karthik NayakJul 27, 2015
  8. Matthieu MoyJul 27, 2015
  9. Karthik NayakJul 27, 2015
  10. 03/11 ref-filter: add option to pad atoms to the rightKarthik Nayak, Jul 27, 2015
  11. Matthieu MoyJul 27, 2015
  12. Junio C HamanoJul 27, 2015
  13. Matthieu MoyJul 27, 2015
  14. Karthik NayakJul 27, 2015
  15. Matthieu MoyJul 27, 2015
  16. Karthik NayakJul 27, 2015
  17. Junio C HamanoJul 27, 2015
  18. Karthik NayakJul 27, 2015
  19. Eric SunshineJul 28, 2015
  20. Karthik NayakJul 29, 2015
  21. 04/11 ref-filter: add option to filter only tagsKarthik Nayak, Jul 27, 2015
  22. 05/11 ref-filter: support printing N lines from tag annotationKarthik Nayak, Jul 27, 2015
  23. 06/11 ref-filter: add support to sort by versionKarthik Nayak, Jul 27, 2015
  24. 07/11 ref-filter: add option to match literal patternKarthik Nayak, Jul 27, 2015
  25. Matthieu MoyJul 27, 2015
  26. Karthik NayakJul 27, 2015
  27. Karthik NayakJul 27, 2015
  28. Matthieu MoyJul 27, 2015
  29. Karthik NayakJul 27, 2015
  30. Eric SunshineJul 28, 2015
  31. Karthik NayakJul 29, 2015
  32. Karthik NayakJul 30, 2015
  33. 08/11 tag.c: use 'ref-filter' data structuresKarthik Nayak, Jul 27, 2015
  34. 09/11 tag.c: use 'ref-filter' APIsKarthik Nayak, Jul 27, 2015
  35. 10/11 tag.c: implement '--format' optionKarthik Nayak, Jul 27, 2015
  36. 11/11 tag.c: implement '--merged' and '--no-merged' optionsKarthik Nayak, Jul 27, 2015
  37. Matthieu MoyJul 27, 2015
  38. Karthik NayakJul 27, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.