Bug#846993: vim-gtk3: vimdiff does not compare last lines if editing changes lines

James McCoy jamessan at debian.org
Thu Dec 15 05:05:38 UTC 2016


Control: tag -1 upstream patch
Control: forwarded -1 https://github.com/vim/vim/pull/1329

On Tue, Dec 06, 2016 at 09:53:43PM +0100, Helge Kreutzmann wrote:
> Hello James,
> On Sun, Dec 04, 2016 at 08:22:34PM -0500, James McCoy wrote:
> > On Sun, Dec 04, 2016 at 09:25:41PM +0100, Helge Kreutzmann wrote:
> > > The last two lines are now identical (they only contain the word
> > > »rows«), but vimdiff (in the current version) does not show this. 
> > > 
> > > (This is an artifical case, ordinarily the last line contains many
> > > words, so it is not easy to spot if they are actually identical). 
> > > 
> > > To really see the a proper diff, you need to save the changed file,
> > > quit vim and rerun the vimdiff command from above.
> > 
> > Can't you just run ":diffupdate" instead?
> 
> Thanks for the hint, yes this works.
> 
> However, with older versions of vim this is not necessary, so the
> regression exists.

Agreed.  Tracked down the offending commit and sent a patch upstream.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB



More information about the pkg-vim-maintainers mailing list