Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 18 Oct 2001 17:11:44 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: simple execvp test
Message-ID: <20011018171144.B19399@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3BCECA31 DOT 4FE7AAD2 AT syntrex DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BCECA31.4FE7AAD2@syntrex.com>
User-Agent: Mutt/1.3.21i

On Thu, Oct 18, 2001 at 02:25:21PM +0200, Pavel Tsekov wrote:
>This mail is inspired by an offlist discussion with James Lee about vi
>execution before "cvs commit" command.
>
>Given the following simple test he says nothing happens after he
>executes it, as happens with the "cvs commit" command which fails to
>execute vi with the following error code "cannot exec vi: No such file
>or directory".
>
>#include <unistd.h>
>
>int main() { char *arg[] = { 0 };
>
>execvp("vi", arg);
>
>return 0; }
>
>If he sets for example the EDITOR variable to /usr/bin/vi then cvs
>suceeds in executing vi.
>
>So is this a known problem with execvp assuming that it should search
>the path for the executable.

I can't duplicate any problem with your test case.  It works as expected
for me.  Ditto, cvs.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/