Tooth Pik wrote: > On Wed, May 29, 2013 at 09:33:54PM +0200, Bram Moolenaar wrote: > > > Patch 7.3.1040 > > Problem: Python: Problems with debugging dynamic build. > > Solution: Python patch 1. (ZyX) > > Files: src/if_python.c, src/if_python3.c > > I had hopes this patch would solve the ":py print "hello"" doing > nothing on the first try problem, but, in a fresh empty vim I still > have to do it twice to see the message once > > If it helps, I noticed this: if I do seemingly anything else, then > try the :py print "hello", it shows -- for example if I open an actual > file with actual stuff in it, the message shows on my first attempt > to trigger it -- I also noticed if I simply added an empty line to an > already empty non-existant file, then attempted the message, it shows > > I noticed further this happens in vim, but gvim shows the message on > the first try
I know this happens sometimes when the termresponse isn't read until you type something. This may cause a redraw and some messages to disappear. Try setting t_RV empty in your .vimrc. Just to find out if this is the problem, not to keep it there. Unfortunately I don't know how to fix it. -- hundred-and-one symptoms of being an internet addict: 27. You refer to your age as 3.x. /// Bram Moolenaar -- [email protected] -- 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 --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
