From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Stefan Beller <sbeller@google.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH 3/4] range-diff: make use of different output indicators
Date: Mon, 13 Aug 2018 13:51:35 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1808131348120.71@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180810224923.143625-4-sbeller@google.com>
Hi Stefan,
On Fri, 10 Aug 2018, Stefan Beller wrote:
> This change itself only changes the internal communication and should
> have no visible effect to the user. We instruct the diff code that produces
> the inner diffs to use X, Y, Z instead of the usual markers for new, old
> and context lines
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
> range-diff.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/range-diff.c b/range-diff.c
> index b6b9abac266..6e4192c8e79 100644
> --- a/range-diff.c
> +++ b/range-diff.c
> @@ -38,6 +38,9 @@ static int read_patches(const char *range, struct string_list *list)
>
> argv_array_pushl(&cp.args, "log", "--no-color", "-p", "--no-merges",
> "--reverse", "--date-order", "--decorate=no",
> + "--output-indicator-new=X",
> + "--output-indicator-old=Y",
> + "--output-indicator-context=Z",
> "--no-abbrev-commit", range,
> NULL);
> cp.out = -1;
> @@ -108,8 +111,18 @@ static int read_patches(const char *range, struct string_list *list)
> * we are not interested.
> */
> continue;
> - else
> + else if (line.buf[0] == 'X') {
> + strbuf_addch(&buf, '+');
> + strbuf_add(&buf, line.buf + 1, line.len - 1);
> + } else if (line.buf[0] == 'Y') {
> + strbuf_addch(&buf, '-');
> + strbuf_add(&buf, line.buf + 1, line.len - 1);
> + } else if (line.buf[0] == 'Z') {
> + strbuf_addch(&buf, ' ');
> + strbuf_add(&buf, line.buf + 1, line.len - 1);
> + } else {
> strbuf_addbuf(&buf, &line);
> + }
My preliminary reading (I sadly lack the time to pull your branch and play
with it) suggests that this works, although I have to admit that X/Y/Z
would confuse me in 6 months from now, as they do not really read like
diff markers but like plain text. I could imagine that '>', '<' and '#'
would not impart that confusion on me.
Ciao,
Dscho
>
> strbuf_addch(&buf, '\n');
> util->diffsize++;
> --
> 2.18.0.865.gffc8e1a3cd6-goog
>
>
next prev parent reply other threads:[~2018-08-13 11:51 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 [this message]
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
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=nycvar.QRO.7.76.6.1808131348120.71@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).