As part of the process, vim is launched. Its STDIN and STDOUT are redirected to /dev/null, and its STDERR is redirected to a file. The contents of that file are discarded if vim returns successfully. However, vim is not exiting successfully in your case. vim claims an error happened by returning an exit code of 1. When a non-zero exit code is received, Text::VimColor croaks (displaying the exit code and the contents of the STDERR file). If vim is returning an error because of the warnings, then that's ... unfortunate. (And it's a bug in vim?)
The best solution would be to replace Text::VimColor::_run with a version that creates pseudo TTYs. IPC::Run can help you there.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||