Nazri Ramliy wrote: > On Sun, Feb 22, 2009 at 11:59 PM, WL <izaq...@gmail.com> wrote: >> 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? > > Run strace on vim on another terminal and as soon as that problem > happens see what's up in that strace output. It might give a clue.
You could also attach gdb to the vim process and check the backtrace. -- Andreas. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
