> With this option, you don't need to bother switching which window has diff
> turned on; you can just look at whichever one you need and it will show how
> it differs from the single master window.
I think it is sometimes useful but sometimes not.
I can see which lines are different just
On Friday, October 12, 2018 at 8:38:22 AM UTC-4, Rick Howe wrote:
> In my case, when there are more than 2 windows, which include similar
> contents,
> in a tab page, I always use 'diffthis' on 2 windows and compare between them.
> If I want to switch a window, just use 'diffoff' on either of
On Sat, Oct 13, 2018 at 8:06 PM Bram Moolenaar wrote:
>
>
> We have made great progress increasing test coverage, thanks for
> everybody helping out!
>
> There is one big gap: The GUI code. We usually test by putting text in
> the input buffer, which means we totally bypass all the GUI event
>
We have made great progress increasing test coverage, thanks for
everybody helping out!
There is one big gap: The GUI code. We usually test by putting text in
the input buffer, which means we totally bypass all the GUI event
handling.
For GTK we could inject events at the level of the
Patch 8.1.0473
Problem:User doesn't notice file does not exist when swap file does.
Solution: Add a note that the file cannot be found. Make the "still
running" notice stand out.
Files: src/memline.c
*** ../vim-8.1.0472/src/memline.c 2018-10-07 23:16:33.134616234
Patch 8.1.0472
Problem:Dosinst command has a few flaws.
Solution: Register DisplayIcon, DisplayVersion and Publisher for the
uninstaller. (closes #3485) Don't set 'diffexpr' if internal diff
is supported. Allow for using Vi compatible from the command line.
Hi,
On Sat, Oct 13, 2018 at 1:11 AM Dominique Pellé
wrote:
>
> Here is another use of free memory also found by afl-fuzz
> which may be related to the previous one despite having
> a different stack:
>
Thanks for reporting these. I am able to reproduce the problem.
I am trying to address this
