On Mon, 4 Sep 2006 at 7:40pm, A.J.Mechelynck wrote: > 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. > > > > IIUC, Steve Hall's builds are "without debug information" (though the > ":debug" command should be available). If you are willing to compile Vim > from sources, you can of course set DEBUG=yes -- see > http://users.skynet.be/antoine.mechelynck/vim/compile.htm for details > about how I used to do it.
Thank you, I will try to build one. -- Thanks, Hari __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
