rickhowe

FYI, this is a sample code to implement a line-by-line comparison in vimdiff. ``` set diffexpr=LineByLineCmp() function! LineByLineCmp() let [f1, f2, fo] = [readfile(v:fname_in), readfile(v:fname_new), []] let eq = ''...

Thank you for using the plugin. I reproduced here and found a regression on version 8.9. I will fix it in the next version. Meanwhile, try to modify the line...

Hi, Thank you for using this plugin and proposing the fix. I have not used neovim but now tried to install and find the problem. I would like to fix...

Hi, I agree with your idea to look at all the mode: gui, cterm and term. I changed like this. Could you please try to check if it works? Regards,...

Hi, Thank you for your checking. Yes, this is a different issue. I can not reproduce it in my PC, but if some plugin might get the FileType or ColorSchme...

I have found that vim post-9.0 patches and nvim 0.10.0 have a inline virtual-text feature to realize this. I tried to implement the [plugin](https://github.com/rickhowe/wrapwidth). Hope to help you.

> @rickhowe perhaps dynamically set the colorcolumn with it maybe more outstanding: e.g `if &wrap && !&tw | exe 'setl colorcolumn=' .. (!get(w:, 'wrapwidth', 0) ? '' : (get(w:, 'wrapwidth',...

> it seems you did not trim these spaces ahead wrapped words when reset wrap/linebreak etc? // anyway, looks this a useful plugin, specially if to view, take your time,...

The plugin does not map those keys if already mapped. And, not documented but `g:VDiffDoMapping` can be `0` to disable those key mapping.

Can I close this issue?