On Wed, June 20, 2012 03:23, Gary Johnson wrote: > I don't have all the details on this at the moment, but I ran out of > time to investigate further today. In summary, opening a new line > in a C comment causes Vim to dump core with various messages about > improper freeing of memory. > > To reproduce: > > $ cat baz.c > // order to avoid a message like this: > // > $ vim -N -u NONE baz.c > :so $VIMRUNTIME/ftplugin/c.vim > > With the cursor on the first line, type A and hit Enter twice. I'm > not it's necessary to hit enter twice. It seems to happen more > consistently if the keys are hit in rapid succession.
This might be the same issue, that Dominique just mentioned at http://groups.google.com/group/vim_dev/msg/ffcfa2eed8f2852f So could you please check, whether Dominiques patch fixes that for you? 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
