This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: using external commands in vim causes fork error
> The CYGWIN env. var. only has nontsec different, the other 2 are the
defaults
> (no need to even put them)... those are the 2 differences: your build of
> vim,
> and the nontsec, experiment with changing the later and find if your
> binary is
> the problem.
It was the vim build. After selectively enabling/disabling options, I found
that it was the --enable-tclinterp option that was causing the error.
Luckily I didn't need it.
--
View this message in context: http://www.nabble.com/using-external-commands-in-vim-causes-fork-error-tf4108011.html#a11684114
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/