WL wrote: > Hi, > > The motivation for my question is as follows. I use VIM mainly for C++ > dev on Linux. Over the years it grew to be heavily configured ( > 700 > lines .vimrc) and to use quite a few scripts. > > Recently I'm experiencing "freezes" of VIM. Meaning, while editing or > executing an ex command VIM will freeze. It will not respond to any > further commands. It does not show or update what its doing. Usually I > wait a min. or two and can then cont. working. This leads me to two, > possibly related questions. > > 1. Is there a way to profile VIM so that I could find the culprit > script or .vimrc line? > > 2. Does VIM support a way to display the action its currently doing or > give some kind of feedback that its still alive when performing time > consuming tasks? > > TIA, > Yosi
Which version of Vim are you using? I recommend compiling the latest version of Vim (Vim-7.2.121 as of today) to get all latest bug fixes. For example, following recent patch fixed a endless loop: 7.2.106 endless loop for "]s" in HTML when there are no misspellings Now to answer your questions: > 1. Is there a way to profile VIM so that I could find the culprit > script or .vimrc line? You can profile Vim itself with gprof or you can also profile vim scripts with the profiler builtin feature in Vim (see :help profile). If this feature is built in Vim command :version should output +profile. > 2. Does VIM support a way to display the action its currently doing or > give some kind of feedback that its still alive when performing time > consuming tasks? :help 'verbose' If it hangs, you can also attach with gdb and look at the stack: $ gdb vim PID (gdb) bt where: - vim is the full pathname of the Vim executable (compiled with debug information and without optimization to get useful output with gdb). - PID is the process ID of the Vim process running (which hangs). As someone mentioned, strace may also be useful. -- Dominique --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
