From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, David Aguilar <davvid@gmail.com>,
Dickson Wong <dicksonwong@gmail.com>
Subject: Re: [PATCH] mergetool: reorder vim/gvim buffers in three-way diffs
Date: Thu, 11 Feb 2016 16:44:41 +0100 [thread overview]
Message-ID: <56BCAC69.8030909@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqqlh6szcfk.fsf@gitster.mtv.corp.google.com>
Junio C Hamano venit, vidit, dixit 10.02.2016 18:45:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>>> Second call for help. Any comments on this from anybody other than
>>> the author that I missed to support this change?
>>
>> OK, applied it (on top of next), looks sane and improves the situation
>> for the majority of people who read left to right, then top down and
>> assign buffers 1 2 3 4 "mentally" to local base remote merge windows
>> based on that. Their expectation is met now. Thanks!
>
> Thanks.
>
> Does this mean that I should warn in the release notes that some
> existing users might get their expectation broken but we are going
> ahead anyway because we think most people read left to right and
> then top down? I am OK with saying that--I just wanted to make sure
> we know that it is what we are doing.
I would claim that anyone who notices the difference in buffer numbering
would be positively surprised.
>> (Also, the other vim variants don't need a corresponding change.)
>
> A stupid question while I am here. What are these different
> variants? When reviewing this patch for the first time I tried to
> find where they are documented, but didn't spot anything.
>
> I can see from the code that vimdiff2 variant does not do anything
> special when it is doing a 3-way merge,
It is "vimdiff" without the base window.
> but vimdiff3 variant does
> behave differently when it has $BASE. It does not need a change
> like this because it already arranges and numbers the windows
> sensibly (in other words, we can label this patch as aligning the
> behaviour of vimdiff to that of vimdiff3)?
git log mergetools/vimdiff3
commit 7c147b77d34f072c40b912fafba499727921fa6e
Author: Felipe Contreras <felipe.contreras@gmail.com>
Date: Sun Apr 20 19:24:20 2014 -0500
mergetools: add vimdiff3 mode
It's similar to the default, except that the other windows are hidden.
This ensures that removed/added colors are still visible on the main
merge window, but the other windows not visible.
Specially useful with merge.conflictstyle=diff3.
I have to say I'm still not sure what it is about (even after trying it
out, even with the conflictstyle config)).
In any case, the buffer numbering is not the same (it is local remote
base merge) but it doesn't matter in this case because only one window
is displayed, so there is no visual association.
Michael
next prev parent reply other threads:[~2016-02-11 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 2:18 [PATCH] mergetool: reorder vim/gvim buffers in three-way diffs Dickson Wong
2016-01-29 18:45 ` Junio C Hamano
2016-02-09 22:25 ` Junio C Hamano
2016-02-10 14:40 ` Michael J Gruber
2016-02-10 17:45 ` Junio C Hamano
2016-02-11 15:44 ` Michael J Gruber [this message]
2016-02-11 16:03 ` Junio C Hamano
2016-02-11 19:24 ` Dickson Wong
2016-02-11 19:31 ` Junio C Hamano
2016-02-11 20:10 ` Dickson Wong
2016-02-11 21:15 ` David Aguilar
2016-02-12 18:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56BCAC69.8030909@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=davvid@gmail.com \
--cc=dicksonwong@gmail.com \
--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).