I have been using Vim for years, and this is a first. It is hanging on a Win7 PC. When it happens, the CPU gets pegged and I have to forcibly kill Vim.
With this code snippet, it always happens when I type the '=' at the end of the
line below. (I blanked out my variables names in this code example. That
doesn't have an effect on the problem.)
switch (P________e)
{
case P______________________a:
{
// Check for compatible Specification Revision
if (((1 << R_____________r->S___________________n) &
S___________________n.A_____________________s) =
{
// TODO
}
It doesn't always happen with an '=' at the end of a line, but when it does
happen, it is when I type and '=' at the end of the line.
It does not happen when I change the code to this...
switch (P________e)
{
case P______________________a:
{
// Check for compatible Specification Revision
if (((1 << a->b) &
d.e) =
{
// TODO
}
Or this...
switch (P________e)
{
case P______________________a:
{
// Check for compatible Specification Revision
if (((1 << a->b) &
dddddd.eeee) =
{
// TODO
}
How do I start debugging/isolating the problem? Is there a way to debug once
Vim is hung? Is there a way to get it un-hung?
I don't use many plugins, but I am using a few.
When it happens, and I press the red X-button on the Win7 window, it does ask
if I want to save my changes. And the save is performed, and the window does
close.
I attached my _vimrc file.
Thanks,
Bill Waters
--
You received this message from the "vim_use" 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
_vimrc
Description: _vimrc
