Hari Krishna Dara wrote: > My older version of perforce plugin was opening another buffer during > FileChangedRO, which was OK in Vim6.3, but since Vim7.0 doesn't allow > this (results in E788), I workedaround this issue in a different way. > My question is actually about the possibility of E788 causing a crash in > Vim, as after seen this error a couple of times (first when my plugin > tried to open a window, and second time when it tried to change the > window) while handling the same FileChangedRO event, Vim ended up > crashing very often. I don't have this problem causing code anymore, > but if there is a debug version of win32 GUI vim for download, I can > probably get the old code back from my SCM and try to reproduce it to > give some insight into the location of the crash.
Vim should not crash, even when you do something wrong. So you experienced these crashes _after_ getting the error message for E788? Strange. If you know how to reproduce this, let me know. I don't know of a Win32 debug Vim available for download. For debugging it would be simplest to get the free version of Visual C++ and build Vim yourself. Or use gcc/gdb in Cygwin or MingW. -- Not too long ago, cut and paste was done with scissors and glue... /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
