From: Fernando Ramos <greenfoo@u92.eu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, mklein994@gmail.com
Subject: Re: [PATCH] vimdiff: make layout engine more robust against user vim settings
Date: Sat, 9 Jul 2022 00:37:47 +0200 [thread overview]
Message-ID: <YsixuwhSwTCapW5L@zacax395.localdomain> (raw)
In-Reply-To: <xmqqsfnbuzrl.fsf@gitster.g>
On 22/07/08 01:15PM, Junio C Hamano wrote:
>
> Interesting. Does that mean that the end-user setting that was
> problematic with the new layout engine would have also broken the
> layout before your series?
Surprisingly enough, no. Turns out the commands used before the new layout
engine was introduced did *not* use 'split' nor 'vertical split' (which are the
commands affected by those two global settings).
Instead, it relayed on the fact that 'vim -d' always opens splits vertically and
then readjusted window positions with 'wincmd [HJKL]'.
The old way was limited in the amount of things that could be achieved and
that's why it was changed... but I completely missed those two global settings
capable of changing the behaviour of the new commands.
> > In order to fix this we can append special keyword 'letfabove' to each
>
> Presumably "leftabove" was meant here.
You are right. Sorry.
> Will queue. Thanks.
Thank you!
prev parent reply other threads:[~2022-07-08 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:10 [PATCH] vimdiff: make layout engine more robust against user vim settings Fernando Ramos
2022-07-08 18:14 ` Fernando Ramos
2022-07-08 20:15 ` Junio C Hamano
2022-07-08 22:37 ` Fernando Ramos [this message]
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=YsixuwhSwTCapW5L@zacax395.localdomain \
--to=greenfoo@u92.eu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox