From: Stefan Beller <sbeller@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/3] diff.c: add --output-indicator-{new, old, context}
Date: Mon, 20 Aug 2018 12:39:59 -0700 [thread overview]
Message-ID: <CAGZ79kY8oadQ2nKWr7znMa8QJgLcidb0FefPDBaba+q2J=nfPg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1808202129420.73@tvgsbejvaqbjf.bet>
On Mon, Aug 20, 2018 at 12:31 PM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> Hi Stefan,
>
> On Fri, 17 Aug 2018, Stefan Beller wrote:
>
> > This will prove useful in range-diff in a later patch as we will be able
> > to differentiate between adding a new file (that line is starting with
> > +++ and then the file name) and regular new lines.
> >
> > It could also be useful for experimentation in new patch formats, i.e.
> > we could teach git to emit moved lines with lines other than +/-.
>
> Thanks.
>
> > diff --git a/diff.c b/diff.c
> > index c5c7739ce34..03486c35b75 100644
> > --- a/diff.c
> > +++ b/diff.c
> > @@ -1281,7 +1281,9 @@ static void emit_diff_symbol_from_struct(struct diff_options *o,
> > else if (c == '-')
> > set = diff_get_color_opt(o, DIFF_FILE_OLD);
> > }
> > - emit_line_ws_markup(o, set_sign, set, reset, ' ', line, len,
> ^
> Here we already pass `o`... so...
>
> > + emit_line_ws_markup(o, set_sign, set, reset,
> > + o->output_indicators[OUTPUT_INDICATOR_CONTEXT],
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ... here, we could simply pass `OUTPUT_INDICATOR_CONTEXT` and let the
> callee look it up in`o->output_indicators[]`...
>
> I read all three patches and did not see a reason why we could not
> simplify the code that way.
>
> Other than that: great!
Thanks!
I considered it, but was put off by the (small) effort of yet another
diff refactoring.
I'll include it in a resend if a resend is needed, otherwise
I would suggest to make it a patch on top?
Thanks,
Stefan
next prev parent reply other threads:[~2018-08-20 19:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 22:49 [PATCH 0/4] Better colors in range-diff! Stefan Beller
2018-08-10 22:49 ` [PATCH 1/4] diff.c: emit_line_0 to take string instead of first sign Stefan Beller
2018-08-13 11:42 ` Johannes Schindelin
2018-08-13 18:19 ` Stefan Beller
2018-08-10 22:49 ` [PATCH 2/4] diff.c: add --output-indicator-{new, old, context} Stefan Beller
2018-08-13 11:47 ` Johannes Schindelin
2018-08-13 18:23 ` Stefan Beller
2018-08-10 22:49 ` [PATCH 3/4] range-diff: make use of different output indicators Stefan Beller
2018-08-13 11:51 ` Johannes Schindelin
2018-08-13 18:24 ` Stefan Beller
2018-08-10 22:49 ` [PATCH 4/4] range-diff: indent special lines as context Stefan Beller
2018-08-13 11:54 ` Johannes Schindelin
2018-08-13 18:36 ` Stefan Beller
2018-08-14 18:54 ` Johannes Schindelin
2018-08-14 19:05 ` Stefan Beller
2018-08-16 8:22 ` Johannes Schindelin
2018-08-17 20:43 ` [PATCH 0/3] Better colors in range-diff Stefan Beller
2018-08-17 20:43 ` [PATCH 1/3] diff.c: add --output-indicator-{new, old, context} Stefan Beller
2018-08-20 19:31 ` Johannes Schindelin
2018-08-20 19:39 ` Stefan Beller [this message]
2018-08-21 16:13 ` Johannes Schindelin
2018-08-22 22:25 ` [PATCH] diff.c: pass sign_index to emit_line_ws_markup Stefan Beller
2018-08-23 14:26 ` Johannes Schindelin
2018-08-17 20:43 ` [PATCH 2/3] range-diff: make use of different output indicators Stefan Beller
2018-08-17 20:43 ` [PATCH 3/3] range-diff: indent special lines as context Stefan Beller
2018-08-17 22:04 ` [PATCH 0/3] Better colors in range-diff Junio C Hamano
2018-08-17 22:09 ` Stefan Beller
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='CAGZ79kY8oadQ2nKWr7znMa8QJgLcidb0FefPDBaba+q2J=nfPg@mail.gmail.com' \
--to=sbeller@google.com \
--cc=Johannes.Schindelin@gmx.de \
--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).