X-Spam-Check-By:	sourceware.org
Message-ID:	<11684114.post@talk.nabble.com>
Date:	Thu, 19 Jul 2007 00:59:27 -0700 (PDT)
From:	nanothief <nanothief AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: using external commands in vim causes fork error
In-Reply-To:	<f7mp3u$ivt$1@sea.gmane.org>
MIME-Version:	1.0
X-Nabble-From:	nanothief AT gmail DOT com
References:	<11681959 DOT post AT talk DOT nabble DOT com> <f7mp3u$ivt$1 AT sea DOT gmane DOT org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> 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/

- Raw text -