Christian Brabandt wrote: > > > On Di, 19 Jan 2016, Bram Moolenaar wrote: > > > > > > > Christian Brabandt wrote: > > > > > > > > > Hi, > > > > > consider this file: > > > > > > > > > > #v+ > > > > > ~$ cat file > > > > > # first comment line > > > > > # second comment line > > > > > ~$ vim -u NONE -N file > > > > > :set hls > > > > > /^\%1l#.* > > > > > (this matches the first line) > > > > > /\%1l^#.* > > > > > (this does not match the first line) > > > > > /^#.*\%1l > > > > > (this matches the first line) > > > > > #v- > > > > > > > > > > The 'regexpengine' setting does not matter, both engines seem to > > > > > behave > > > > > the same, however I find it kind of unexpected, that the second > > > > > search > > > > > term does not match. > > > > > > > > It looks like the zero-width match clears the flag that the current > > > > position is at the start of the line. I would call that a bug. > > > > > > Yes you are right and I wouldn't bet the problem only occurs here. > > > However here is a patch. > > > > When I include the test change, the test hangs. > > I do not see this. Or is this a different test that hangs?
No, it somehow keeps looping. > Hm, with a missing +eval, the test fails. Anyhow, here is the patch with > a test, that has the line numbers hardwired. Thanks for the quick reply. This one works. -- Google is kind of like Dr. Who's Tardis; it's weirder on the inside than on the outside... /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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.
