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: Wed, 7 Nov 2001 20:36:12 +0100
From: Alessandro Doro <adoroo AT tin DOT it>
To: cygwin AT cygwin DOT com
Subject: VIM "Cannot execute shell sh", "long startup time" problems maybe solved
Message-ID: <20011107203612.B363921@SNU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i

I found that vim really tries to spawn sh (or $SHELL) during startup
and when loading files in a DOS session.
This happens when the HOME environment variable is not set.
Note that E79 messages disappear if sh (or the SHELL pointed by $SHELL)
is in your PATH; vim launches the shell (*only if HOME is not set*)
and startup time increases, depending on (don't know how) your .vimrc
(more generally file loading time increases).

In order to reproduce the behaviour you can start a regular bash
session, unset HOME then start vim. You can also experiment with
SHELL values or unsetting it.


A few hints:

1.
add the HOME variable to the environment
(1.3.4 cygwin1.dll sets it for you now!!!)

2.
add cygwin binaries path to PATH when running cygwin programs
inside a DOS shell; sometimes (always, with vim) is a good job to do.


Excuse me for any imprecision or error: fast analysis, fast typing,
bad english.
Note: I'm using vim 6.0.11-1 on W95.


Bye, Alessandro.


-- 
 
                                   ad
   le castagne scottano... (and so on)
______________________________________

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