Loading ...
Sorry, an error occurred while loading the content.

Re: new regexp engine bug?

Expand Messages
  • Bram Moolenaar
    ... Thanks for reporting. It s easy to reproduce. Strange that this wasn t caught before. Looks like the actual problem is matching ^ after n. -- A bad peace
    Message 1 of 3 , Jun 13, 2013
    • 0 Attachment
      SungHyun Nam wrote:

      > $ cat test
      >
      > a
      > b
      > c
      >
      > $ vim -u NONE --noplugin test
      > /a\n\(^b$\n\)\{1,2}c
      >
      > The search failed with re=0. If I set 're=1', search works.

      Thanks for reporting. It's easy to reproduce.
      Strange that this wasn't caught before.

      Looks like the actual problem is matching ^ after \n.

      --
      A bad peace is better than a good war. - Yiddish Proverb

      /// Bram Moolenaar -- Bram@... -- 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 vim_dev+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    Your message has been successfully submitted and would be delivered to recipients shortly.