On Wed, Jun 18, 2014 at 12:24 AM, tooth pik <[email protected]> wrote: > On Tue, Jun 17, 2014 at 11:43:35PM +0200, Dominique Pellé wrote: >> Bram Moolenaar <[email protected]> wrote: > >> > John Marriott wrote: >> > >> >> On 18-Jun-2014 1:49 AM, Bram Moolenaar wrote: >> >> > Patch 7.4.330 >> >> > Problem: Using a regexp pattern to highlight a specific position can >> >> > be >> >> > slow. >> >> > Solution: Add matchaddpos() to highlight specific positions >> >> > efficiently. >> >> > (Alexey Radkov) >> >> > Files: runtime/doc/eval.txt, runtime/doc/usr_41.txt, >> >> > runtime/plugin/matchparen.vim, src/eval.c, src/ex_docmd.c, >> >> > src/proto/window.pro, src/screen.c, src/structs.h, >> >> > src/testdir/test63.in, src/testdir/test63.ok, src/window.c >> >> > >> >> > ... >> >> Hi All, >> >> >> >> After applying this patch, the cursorline display does not show for 2 >> >> characters starting at the cursor position, if the line is empty. >> >> To repro, open a empty file and turn on cursorline. >> > >> > I do not see the problem. Anything in your setup that matters? > >> I do not see this bug either. > > I do -- I am building "normal" size vim currently, using colo biogoo for > gvim and a terminal biogoo created with CSAApprox > > actually that's probably not relevant -- I tried > > gvim -u NONE -c 'set cursorline' > > and still saw the problem using the default colorscheme > > the first two characters do not show the highlight background > >> But I just posted a patch >> which fixes valgrind error introduced by vim-7.3.330. >> I'm curious whether my patch also fixes the bug with >> current line reported by John. > >> See email in vim-dev with subject: [patch] fixed valgrind >> errors introduced by vim-7.4.330. > > maybe...
I can now reproduce the bug: current line not being highlighted in the first 2 characters. It happens with: $ vim -f -g -u NONE -c 'set cul' The patch I sent earlier appears to fix it. See subject: subject: [patch] fixed valgrind errors introduced by vim-7.4.330. Regards Dominique -- -- 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.
