On 6 April 2010 21:52, H.P. Logsdon wrote: > > On occasion while trying to insert a newline, either by returning, in insert > mode, at the end of an existing line or by Shift+"o", for inserting before > current line or "o" to insert after current line, the current buffer will > freeze. I run the same universal build (~Jan 15th, 2010) on both a 32-bit > coreduo MBP and a 64-bit capable c2d iMac, and both seem to have the same > problem. When "frozen", the menu bar, system bar, and key shortcuts work > (cmd+q, etc), but I cannot get any response from the buffer.
It means that the Vim process (note that MacVim spawn a Vim process for each window you open) has hung. Can you get it "unstuck" by Ctrl-C? How about Cmd-.? To me this sounds like a plugin that is causing the problem (it is as if some processing is done when you insert a new line). > By random, I mean I cannot reliably get MacVim to hang while editing on any > file, but once I do get it to hang, I can force close MacVim, reopen, either > recovering the swap file or discarding, go to the line I previously was > editing, and try to insert a newline again, and it will repeatably hang the > buffer. My only solution so far has been to use terminal vim to edit the > file. As soon as I do, I can usually save from terminal vim and continue in > MacVim. Have you tried moving .[g]vimrc and ~/.vim out of the way and restarting after you are able to repeat the bug? > This afternoon, I pulled from git and recompiled both with Release and Debug. > Both have the same issue, and since the application is still responsive, but > the buffer is not, I cannot get a peep out of GDB when configured as Debug. Try attaching GDB to the Vim process that is stuck (not the MacVim process) -- can you see where it is hung? (My guess is that it will be in a loop waiting for keyboard input.) > I've wiped my .gvimrc, .vim/ and .vimrc files/directory multiple times, and > it seems to persist. Occasionally, I will get output to my > /var/log/system.log, as seen below, but not always. The output shows me that the Vim process is stuck (the MacVim process tries to send it input and failing every time) and then you quit MacVim resulting in the last two complaints about "connection was lost" from the Vim process (indicating that it has not crashed but is in fact stuck in a loop...unless those were logged from other Vim processes...I can't tell which from the logs). > I'm currently at a loss of what to try next. I'm most interested in what happens if you wipe your rc-files and .vim directory _after_ you can reliably replicate the bug. If that does not get the problem to go away I'd like to know where the process got stuck (by attaching with GDB). Thanks, Björn -- You received this message from the "vim_mac" 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 To unsubscribe, reply using "remove me" as the subject.
