On Saturday, July 9, 2016 at 5:20:16 AM UTC+9, Bram Moolenaar wrote:
> I wrote:
>
> > Patch 7.4.2003
> > Problem:Still cursor flickering when a callback updates the screen.
> > (David
> > Samvelyan)
> > Solution: Put the cursor in the right position after updating the screen.
>
Patch 8.0.0020
Problem:The regexp engines are not reentrant.
Solution: Add regexec_T and save/restore the state when needed.
Files: src/regexp.c, src/regexp_nfa.c, src/testdir/test_expr.vim,
runtime/doc/eval.txt, runtime/doc/change.txt
*** ../vim-8.0.0019/src/regexp.c
Patch 8.0.0021
Problem:In the GUI when redrawing the cursor it may be on the second half
of a double byte character.
Solution: Correct the cursor column. (Yasuhiro Matsumoto)
Files: src/screen.c
*** ../vim-8.0.0020/src/screen.c2016-08-29 22:42:20.0 +0200
--
Yasuhiro Matsumoto wrote:
> On Saturday, July 9, 2016 at 5:20:16 AM UTC+9, Bram Moolenaar wrote:
> > I wrote:
> >
> > > Patch 7.4.2003
> > > Problem:Still cursor flickering when a callback updates the screen.
> > > (David
> > > Samvelyan)
> > > Solution: Put the cursor in the
On Tuesday, August 16, 2016 at 11:45:15 PM UTC-5, Gabriel wrote:
> Hello,
>
> I'm an Arch Linux user, experiencing a strange bug that's not reported
> by anyone else on the Arch Forums.
>
> On upgrading gvim to gvim-7.4.2143-1-x86_64, I experienced intermittent
> lag when navigating up/down (i.e.
Hi.
There are 2 problems about job-channel callback.
1) callback isn't invoked when last line doesn't terminate by NL.
[repro steps]
test.vim
---
function! Callback(ch, msg)
echom a:msg
let g:linecount += 1
endfunction
let g:linecount = 0
call job_start(['python', '-c', 'import sys;sys.s
On Monday, October 3, 2016 at 7:49:20 AM UTC+9, Ozaki Kiichi wrote:
>
> https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cca137
Bram, in this patch, you can see workaround to avoid a bug with escaping
double-quote on Windows.
https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cc
The patch from Ozaki (posted at
https://groups.google.com/d/msg/vim_dev/LhXQJusQScM/_wV4u5y5AAAJ, in
https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cca137) fixes this
(only looked at the test suite for Neomake without the "sleep .05" hack).
--
--
You received this message from the
