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

Re: E315 errors in Vim 74a (folding, Python, buffers)

Expand Messages
  • Vlad Irnov
    ... I am happy to confirm that these types of issues are fixed in vim-7-4a-044. Thanks. Regards, Vlad -- -- You received this message from the vim_dev
    Message 1 of 7 , Jul 25, 2013
    • 0 Attachment
      On 7/23/13, Bram Moolenaar <Bram@...> wrote:
      >
      > Vlad Irnov wrote:
      >
      >> I confirm that this issue has been fixed by Patch 7.4a.027 and
      >> subseqent, but only partially.
      >> The same errors can occur when Python deletes lines in another buffer.
      >> The following tests show how to reproduce (also attached).
      >> Tested with Vim 7.4a BETA, patches 1-39, compiled with MinGW, Windows 8.
      >>
      >> "---vim74a_E315_test2.vim-----------------------------
      >> tabnew BUFFER1
      >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
      >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
      >> " 'splitbelow' is needed to get ml_get errors.
      >> set splitbelow
      >> new BUFFER2
      >> py import vim
      >> py B2=vim.current.buffer
      >> wincmd p
      >> py B2[0]='BUFFER2...'
      >> for i in range(10)
      >> py B2.append(['xxx','yyy'])
      >> py del B2[-1]
      >> endfor
      >> " Multiple errors 'E315: ml_get: invalid lnum: 3'.
      >> " Folding is wrong in BUFFER1--there are no folds.
      >>
      >>
      >> "---vim74a_E315_test3.vim-----------------------------
      >> tabnew BUFFER1
      >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
      >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
      >> new BUFFER2
      >> py import vim
      >> py B2=vim.current.buffer
      >> wincmd p
      >> py B2.append(['xxx','yyy'])
      >> " This does not cause ml_get errors, but disrupts folding.
      >> py del B2[-1]
      >> " Folds are now wrong in BUFFER1.
      >
      > Thanks for reproducing another problem. I'll add it to the todo list.

      I am happy to confirm that these types of issues are fixed in
      vim-7-4a-044. Thanks.
      Regards,
      Vlad

      --
      --
      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.
    • mirek186@...
      ... I can report that I still have this bug in build vim-7-4-052 from repo: https://launchpad.net/~dgadomski/+archive/vim-daily -- -- You received this message
      Message 2 of 7 , Oct 16, 2013
      • 0 Attachment
        On Friday, 26 July 2013 06:23:18 UTC+1, Vlad Irnov wrote:
        > On 7/23/13, Bram Moolenaar <Bram@...> wrote:
        >
        > >
        >
        > > Vlad Irnov wrote:
        >
        > >
        >
        > >> I confirm that this issue has been fixed by Patch 7.4a.027 and
        >
        > >> subseqent, but only partially.
        >
        > >> The same errors can occur when Python deletes lines in another buffer.
        >
        > >> The following tests show how to reproduce (also attached).
        >
        > >> Tested with Vim 7.4a BETA, patches 1-39, compiled with MinGW, Windows 8.
        >
        > >>
        >
        > >> "---vim74a_E315_test2.vim-----------------------------
        >
        > >> tabnew BUFFER1
        >
        > >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
        >
        > >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
        >
        > >> " 'splitbelow' is needed to get ml_get errors.
        >
        > >> set splitbelow
        >
        > >> new BUFFER2
        >
        > >> py import vim
        >
        > >> py B2=vim.current.buffer
        >
        > >> wincmd p
        >
        > >> py B2[0]='BUFFER2...'
        >
        > >> for i in range(10)
        >
        > >> py B2.append(['xxx','yyy'])
        >
        > >> py del B2[-1]
        >
        > >> endfor
        >
        > >> " Multiple errors 'E315: ml_get: invalid lnum: 3'.
        >
        > >> " Folding is wrong in BUFFER1--there are no folds.
        >
        > >>
        >
        > >>
        >
        > >> "---vim74a_E315_test3.vim-----------------------------
        >
        > >> tabnew BUFFER1
        >
        > >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
        >
        > >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
        >
        > >> new BUFFER2
        >
        > >> py import vim
        >
        > >> py B2=vim.current.buffer
        >
        > >> wincmd p
        >
        > >> py B2.append(['xxx','yyy'])
        >
        > >> " This does not cause ml_get errors, but disrupts folding.
        >
        > >> py del B2[-1]
        >
        > >> " Folds are now wrong in BUFFER1.
        >
        > >
        >
        > > Thanks for reproducing another problem. I'll add it to the todo list.
        >
        >
        >
        > I am happy to confirm that these types of issues are fixed in
        >
        > vim-7-4a-044. Thanks.
        >
        > Regards,
        >
        > Vlad

        I can report that I still have this bug in build vim-7-4-052 from repo:
        https://launchpad.net/~dgadomski/+archive/vim-daily

        --
        --
        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.
      • Vlad Irnov
        ... I cannot reproduce with Vim 7-4-052, 32-bit, compiled with MinGW, Windows 8. No problems at all. I did not have a chance to run tests on Linux though. Are
        Message 3 of 7 , Oct 17, 2013
        • 0 Attachment
          On 10/16/13, mirek186@... <mirek186@...> wrote:
          > On Friday, 26 July 2013 06:23:18 UTC+1, Vlad Irnov wrote:
          >> On 7/23/13, Bram Moolenaar <Bram@...> wrote:
          >>
          >> >
          >>
          >> > Vlad Irnov wrote:
          >>
          >> >
          >>
          >> >> I confirm that this issue has been fixed by Patch 7.4a.027 and
          >>
          >> >> subseqent, but only partially.
          >>
          >> >> The same errors can occur when Python deletes lines in another buffer.
          >>
          >> >> The following tests show how to reproduce (also attached).
          >>
          >> >> Tested with Vim 7.4a BETA, patches 1-39, compiled with MinGW, Windows
          >> >> 8.
          >>
          >> >>
          >>
          >> >> "---vim74a_E315_test2.vim-----------------------------
          >>
          >> >> tabnew BUFFER1
          >>
          >> >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
          >>
          >> >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
          >>
          >> >> " 'splitbelow' is needed to get ml_get errors.
          >>
          >> >> set splitbelow
          >>
          >> >> new BUFFER2
          >>
          >> >> py import vim
          >>
          >> >> py B2=vim.current.buffer
          >>
          >> >> wincmd p
          >>
          >> >> py B2[0]='BUFFER2...'
          >>
          >> >> for i in range(10)
          >>
          >> >> py B2.append(['xxx','yyy'])
          >>
          >> >> py del B2[-1]
          >>
          >> >> endfor
          >>
          >> >> " Multiple errors 'E315: ml_get: invalid lnum: 3'.
          >>
          >> >> " Folding is wrong in BUFFER1--there are no folds.
          >>
          >> >>
          >>
          >> >>
          >>
          >> >> "---vim74a_E315_test3.vim-----------------------------
          >>
          >> >> tabnew BUFFER1
          >>
          >> >> call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
          >>
          >> >> setl fdm=marker fdt=getline(v:foldstart) fdl=0
          >>
          >> >> new BUFFER2
          >>
          >> >> py import vim
          >>
          >> >> py B2=vim.current.buffer
          >>
          >> >> wincmd p
          >>
          >> >> py B2.append(['xxx','yyy'])
          >>
          >> >> " This does not cause ml_get errors, but disrupts folding.
          >>
          >> >> py del B2[-1]
          >>
          >> >> " Folds are now wrong in BUFFER1.
          >>
          >> >
          >>
          >> > Thanks for reproducing another problem. I'll add it to the todo list.
          >>
          >>
          >>
          >> I am happy to confirm that these types of issues are fixed in
          >>
          >> vim-7-4a-044. Thanks.
          >>
          >> Regards,
          >>
          >> Vlad
          >
          > I can report that I still have this bug in build vim-7-4-052 from repo:
          > https://launchpad.net/~dgadomski/+archive/vim-daily


          I cannot reproduce with Vim 7-4-052, 32-bit, compiled with MinGW,
          Windows 8. No problems at all. I did not have a chance to run tests on
          Linux though. Are you sure your Vim is really version 7-4-052? You can
          check with :version.

          Regards,
          Vlad

          --
          --
          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.