Try such to make sure its not any VimL code or non standard
configuration.
vim -u NONE -U NONE -N
If it is Vim code gdb will be very awkward to solve your issue.
Then you have to enable/disable your plugins or code snippets to see
which is causing the issue.
If it is not VimL you may also use strace to see what vim is actually
doing (causing 100% CPU).
If it is not VimL try to start gvim without X:
DISPLAY= gvim
(by not setting DISPLAY gvim will start as vim and show an error
message)
to verify it is related to the 'gui' feature.
Marc Weber
--
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
Sunday, October 28, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment