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

Re: [PATCH] Make pyeval() print stack traces (unless :silence’d)

Expand Messages
  • ZyX
    Wondering what’s the status of this patch? I don’t see it in most recent todo.txt. It would be very fine to include as debugging code that uses `pyeval()
    Message 1 of 4 , Jan 20, 2013
    • 0 Attachment
      Wondering what’s the status of this patch? I don’t see it in most recent todo.txt.

      It would be very fine to include as debugging code that uses `pyeval()' is hard without it (did not create before because for my projects using `vim.bindeval' seems to be easier).

      --
      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
    • Bram Moolenaar
      ... It s in the todo list, at line 102 currently. -- You got to work at a mill? Lucky! I got sent back to work in the acid-mines for my daily crust of stale
      Message 2 of 4 , Jan 21, 2013
      • 0 Attachment
        ZyX wrote:

        > Wondering what’s the status of this patch? I don’t see it in
        > most recent todo.txt.
        >
        > It would be very fine to include as debugging code that uses
        > `pyeval()' is hard without it (did not create before because for my
        > projects using `vim.bindeval' seems to be easier).

        It's in the todo list, at line 102 currently.

        --
        You got to work at a mill? Lucky! I got sent back to work in the
        acid-mines for my daily crust of stale bread... which not even the
        birds would eat.

        /// 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
      • Christian Brabandt
        ... Your version does not seem to have made it into the public available repository yet: http://code.google.com/p/vim/source/browse/runtime/doc/todo.txt#102
        Message 3 of 4 , Jan 22, 2013
        • 0 Attachment
          On Mon, January 21, 2013 21:06, Bram Moolenaar wrote:
          >
          > ZyX wrote:
          >
          >> Wondering what’s the status of this patch? I don’t see it in
          >> most recent todo.txt.
          >>
          >> It would be very fine to include as debugging code that uses
          >> `pyeval()' is hard without it (did not create before because for my
          >> projects using `vim.bindeval' seems to be easier).
          >
          > It's in the todo list, at line 102 currently.

          Your version does not seem to have made it into the public
          available repository yet:
          http://code.google.com/p/vim/source/browse/runtime/doc/todo.txt#102

          regards,
          Christian

          --
          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
        Your message has been successfully submitted and would be delivered to recipients shortly.