Reputation: 10393
I am attempting to debug a misbehaving Vim plug-in that is apparently writing stuff to stdout and stderr, but since gVim seems to launch in a separate process when run from the command line, I have to way to inspect it. Is there any solution?
Upvotes: 2
Views: 789
Reputation: 172540
As it's hard to write to stdout / stderr from Vimscript, I doubt that this is what the plugin does.
In any way, hardly any plugin is GVIM-only, so you can just launch terminal Vim to capture the output.
To troubleshoot the misbehaving plugin, I recommend to capture a verbose log with vim -V20vimlog
.
If that doesn't suffice, you can step through the plugin, e.g. with :breakadd file plugin/pluginname.vim
. Finally, don't hesitate to contact the plugin's author; he's best suited to help you.
Upvotes: 2