If you have got this question in your mind, then you are in right place.

vim -V20  2>&1 |tee

You can give the debugfile as any file, where you would want to log the debug messages. This will log a lot of information in the debugfile, you can open the file, once you have got the error in the main vim window. After this, you can open the debugfile and simply search for the error that you were getting. Just look for the reason why this error is originated in the debug logs and then it should be pretty simple to fix that.

Related articles

• In and out Vim Ex-mode
• Introducing dispatch.vim – the asynchronous build and test dispatcher
• Vim Splits – Move Faster and More Naturally

Related Articles:

• 2010/08/02   when you press f9 ‘paste’ is on , press f9 again and ‘paste’ is off, and so forth (works in insert-mode and command-mode)
• 2011/09/04   debug call function() to debug a function in vim
• 2012/08/06   vim mappings for multiple files.
• 2012/03/14   cream bash ide – vim with bash support
• 2011/11/05   g flag in :s useless in vim