From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>, 刘炜 <lw17qhdz@gmail.com>
Subject: Re: [PATCH] xdiff: unignore changes in function context
Date: Thu, 05 Dec 2019 09:29:46 -0800 [thread overview]
Message-ID: <xmqq5ziu1y0l.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <3053f7a8-0723-aaa7-fe43-9b8b13b2e259@web.de> ("René Scharfe"'s message of "Thu, 5 Dec 2019 17:15:31 +0100")
René Scharfe <l.s.r@web.de> writes:
> Changes involving only blank lines are hidden with --ignore-blank-lines,
> unless they appear in the context lines of other changes. This is
> handled by xdl_get_hunk() for context added by --inter-hunk-context, -u
> and -U.
>
> Function context for -W and --function-context added by xdl_emit_diff()
> doesn't pay attention to such ignored changes; it relies fully on
> xdl_get_hunk() and shows just the post-image of ignored changes
> appearing in function context. That's inconsistent and confusing.
>
> Improve the result of using --ignore-blank-lines and --function-context
> together by fully showing ignored changes if they happen to fall within
> function context.
>
> Signed-off-by: René Scharfe <l.s.r@web.de>
> ---
> t/t4015-diff-whitespace.sh | 6 +-----
> xdiff/xemit.c | 17 +++++++++++++++++
> 2 files changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/t/t4015-diff-whitespace.sh b/t/t4015-diff-whitespace.sh
> index eadaf57262..5888ae5ed3 100755
> --- a/t/t4015-diff-whitespace.sh
> +++ b/t/t4015-diff-whitespace.sh
> @@ -2025,11 +2025,6 @@ test_expect_success 'compare mixed whitespace delta across moved blocks' '
> test_cmp expected actual
> '
>
> -# Note that the "6" in the expected hunk header below is funny, since we only
> -# show 5 lines (the missing one was blank and thus ignored). This is how
> -# --ignore-blank-lines behaves even without --function-context, and this test
> -# is just checking the interaction of the two features. Don't take it as an
> -# endorsement of that output.
Nice to see that somebody anticipated that we may fix this some day.
> @@ -2039,6 +2034,7 @@ test_expect_success 'combine --ignore-blank-lines with --function-context' '
> cat <<-\EOF >expect &&
> @@ -1,6 +1,4 @@
> 1
> + -
> 2
> 3
> 4
And I think this is a more intuitive outcome people would expect.
> diff --git a/xdiff/xemit.c b/xdiff/xemit.c
> index 30713ae9a9..9d7d6c5087 100644
> --- a/xdiff/xemit.c
> +++ b/xdiff/xemit.c
> @@ -172,10 +172,12 @@ int xdl_emit_diff(xdfenv_t *xe, xdchange_t *xscr, xdemitcb_t *ecb,
> struct func_line func_line = { 0 };
>
> for (xch = xscr; xch; xch = xche->next) {
> + xdchange_t *xchp = xch;
> xche = xdl_get_hunk(&xch, xecfg);
> if (!xch)
> break;
>
> +pre_context_calculation:
> s1 = XDL_MAX(xch->i1 - xecfg->ctxlen, 0);
> s2 = XDL_MAX(xch->i2 - xecfg->ctxlen, 0);
>
> @@ -212,6 +214,21 @@ int xdl_emit_diff(xdfenv_t *xe, xdchange_t *xscr, xdemitcb_t *ecb,
> if (fs1 < s1) {
> s2 = XDL_MAX(s2 - (s1 - fs1), 0);
> s1 = fs1;
> +
> + /*
> + * Did we extend context upwards into an
> + * ignored change?
> + */
> + while (xchp != xch &&
> + xchp->i1 + xchp->chg1 <= s1 &&
> + xchp->i2 + xchp->chg2 <= s2)
> + xchp = xchp->next;
> +
> + /* If so, show it after all. */
> + if (xchp != xch) {
> + xch = xchp;
> + goto pre_context_calculation;
> + }
> }
> }
>
> --
> 2.24.0
next prev parent reply other threads:[~2019-12-05 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 16:15 [PATCH] xdiff: unignore changes in function context René Scharfe
2019-12-05 17:29 ` Junio C Hamano [this message]
2019-12-05 21:09 ` Jeff King
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=xmqq5ziu1y0l.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=lw17qhdz@gmail.com \
--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).