On Fri, Jun 27, 2014 at 2:05 PM, Christian Brabandt <[email protected]> wrote:
> Hm, from a quick look at the problem, it seems that the real problem is
> that scrollbinded windows try to synchronize changes and therefore
> depending on the diff state might scroll another window by more than 1
> line.
>
> In your case, I think it might help to not scrollbind the windows.
That does help making the "unsynchronized" screen rows problem go
away, but only after I move the cursor up and down (jk) after vim
starts.
That is (in a terminal with 25 lines):
$ vimdiff -u NONE -c 'set diffopt-=filler' -c 'windo set nu
noscrollbind' -c $ a b
results in the cursor positioned at the last line (line 40) in the
window on the right, and on the left window the last line shown is
line 23. Hitting "jk" seems to make vim redraws the correct view for
the buffer in the left window.
Looking at the diff shown by vim I can see that vim's diff mode
wasn't designed to show line-by-line differences in the way that I
wanted to - for example line 14 of both file are identical but on the
left window that line has a blue background while in the other window
the background is black.
Thanks for the hint!
nazri
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
