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

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

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

2013-01-12 Fir de Conversatie ZyX
# HG changeset patch # User ZyX kp-...@ya.ru # Date 1358006430 -14400 # Node ID 9c4ad944627dc19bd898174c8fe28a5ee0de4c26 # Parent b89e2bdcc6e516d7e8cbcb3ece9961ffe18b45fa Made pyeval()/py3eval() also print error messages diff -r b89e2bdcc6e5 -r 9c4ad944627d src/if_python.c --- a/src/if_python.c