On Sun, Oct 16, 2011 at 01:31:47AM EDT, Tony Mechelynck wrote:
On 15/10/11 23:53, Frederico Cadete wrote:
I had a similar experience when I recompiled Vim, coming from using
vim as packaged by Ubuntu.
The differences in behaviour were annoying, but they were not because
of the compiling
Assuming you are using this Jamie Moyers's Perl script for coloring
gcc output, it states that
# colorgcc will only emit color codes if:
#
#(1) Its STDOUT is a tty and
#(2) the value of $TERM is not listed in the nocolor option.
When you use it from vim, maybe the script sees that its
Does it need to be gvim? Or can you use console vim (replace gvim in
your external command, with vim)?
I am using gvim as main app in windows.
What I need is to do a libcall in background that I can read the
output of this libcall job.
Can you help me ?
--
You received this message from
