This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

VIM "Cannot execute shell sh", "long startup time" problems maybe solved


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]