67784Re: [PATCH] Make pyeval() print stack traces (unless :silence’d)
- Jan 21, 2013ZyX wrote:
> Wondering what’s the status of this patch? I don’t see it inIt's in the todo list, at line 102 currently.
> 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 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
- << Previous post in topic Next post in topic >>