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

2013-01-21 Fir de Conversatie Bram Moolenaar

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 -- b...@moolenaar.net -- 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


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

2013-01-20 Fir de Conversatie 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()' 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