From: Junio C Hamano <gitster@pobox.com>
To: Matthew Klein <mklein994@gmail.com>, Fernando Ramos <greenfoo@u92.eu>
Cc: git@vger.kernel.org
Subject: Re: Bug with splits in new nvimdiff layout
Date: Thu, 07 Jul 2022 11:46:32 -0700 [thread overview]
Message-ID: <xmqqo7y0zrp3.fsf@gitster.g> (raw)
In-Reply-To: <CACRpdvnuAYY0U1_3uD8zKgtq05+bgwjzXpZKomro6gqYDNrjGg@mail.gmail.com> (Matthew Klein's message of "Thu, 7 Jul 2022 11:58:48 -0500")
Matthew Klein <mklein994@gmail.com> writes:
> Hi,
>
> I encountered a bug when using the new vimdiff layout format.
Thanks for a report.
Fernando (the author of the layout engine)? Can you take a look?
> To recreate this, start with a merge conflict, and merge with this command:
>
> git mergetool --tool=nvimdiff
>
> I expected the layout to be:
>
> ------------------------------------------
> | | | |
> | LOCAL | BASE | REMOTE |
> | | | |
> ------------------------------------------
> | |
> | MERGED |
> | |
> ------------------------------------------
>
> The layout when I ran the command was:
>
> ------------------------------------------
> | |
> | LOCAL |
> | |
> ------------------------------------------
> | | | |
> | LOCAL | LOCAL | MERGED |
> | | | |
> ------------------------------------------
>
> I expected the layout to be the same as what was documented to be the default
> for "nvimdiff".
>
> In my init.vim configuration file, I have these lines set:
>
> set splitbelow
> set splitright
>
> These options globally change the behaviour of the "split" command so that
> instead of "split" creating a new window above the current window, or to the
> left when used with "vertical", it does the opposite. Docs:
> https://neovim.io/doc/user/options.html#'splitbelow'
>
> I recommend using the "leftabove" (a.k.a "aboveleft") command together with
> "split". Since these windows are positioned absolutely (according to
> "mergetool.nvimdiff.layout"), it shouldn't depend on the user's configuration.
> Docs: https://neovim.io/doc/user/windows.html#:leftabove
>
> The previous invocation (i.e. "4wincmd w | wincmd J") didn't run into this
> issue, since its not affected by the "splitbelow" and "splitright" options.
>
> Hope this helps,
>
> Matthew
>
> [System Info]
> git version:
> git version 2.37.0
> cpu: x86_64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Linux 5.18.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 02 Jul 2022
> 21:03:06 +0000 x86_64
> compiler info: gnuc: 12.1
> libc info: glibc: 2.35
> $SHELL (typically, interactive shell): /bin/bash
>
>
> [Enabled Hooks]
next prev parent reply other threads:[~2022-07-07 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 16:58 Bug with splits in new nvimdiff layout Matthew Klein
2022-07-07 18:46 ` Junio C Hamano [this message]
2022-07-08 17:06 ` Fernando Ramos
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=xmqqo7y0zrp3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=greenfoo@u92.eu \
--cc=mklein994@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.