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
X-Apparently-From: <tjclose AT yahoo DOT com>
Message-Id: <5.1.0.14.1.20011105185539.00a28e00@pop.mail.yahoo.com>
X-Sender: tjclose AT pop DOT mail DOT yahoo DOT com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 05 Nov 2001 18:57:19 -0400
To: cygwin AT cygwin DOT com
From: Tyler Close <tjclose AT yahoo DOT com>
Subject: Re: [ANNOUNCEMENT] Updated: vim-6.0.46-1
In-Reply-To: <20011105231710.K17306@cygbert.vinschen.de>
References: <5 DOT 1 DOT 0 DOT 14 DOT 1 DOT 20011105172027 DOT 00a12080 AT pop DOT mail DOT yahoo DOT com>
 <5 DOT 1 DOT 0 DOT 14 DOT 1 DOT 20011105172027 DOT 00a12080 AT pop DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:17 PM 05/11/01 +0100, Corinna Vinschen wrote:
>On Mon, Nov 05, 2001 at 05:40:42PM -0400, Tyler Close wrote:
> > Corinna Vinschen wrote:
> > >What a funny idea.
> >
> > Perhaps, but I am not imagining this behaviour. If you run the Cygwin
> > /bin/vim.exe from an MS-DOS shell, with no .vimrc file, you will get two
> > errors of the type:
> >
> > Cannot execute shell sh
>
>Did you install the ash package?

Yes. Does this mean that vim is supposed to be starting sub-shells?


> > E79: Cannot expand wildcards
> >
> > If you use the /usr/share/vim/vim60/vimrc_example.vim file as your .vimrc,
> > you get a multitude of these errors.
> >
> > With no .vimrc file, starting /bin/vim.exe from the bash shell causes the
> > Cygwin window title to switch between VIM and bash a few times. Using the
> > /usr/share/vim/vim60/vimrc_example.vim, the Cygwin window title changes a
> > multitude of times.
> >
> >
> > >- The .vimrc file does not start any subshell as long as there's no
> > >   :sh commmand or such.
> >
> > Given these two sets of behaviour, it does not seem unreasonable to 
> suppose
> > that /bin/vim.exe is causing several shells to execute. I agree that this
> > should not be happening, but it appears to be the case. I would appreciate
> > it if you would attempt to verify my observations and diagnose the problem.
>
>Sorry but I can't reproduce that.  Neither does the title change nor
>does it show `sh' or `bash' at all (given I have set CYGWIN=...title...).

What version of Windows are you using? I am using Windows 98 (not the 
second edition). I do not have a CYGWIN environment variable set. Changing 
the window title must be the default behaviour under Win98. Below is the 
output of printenv:

# printenv
PROMPT=$p$g
PWD=/dosc/mydocu~1
COMSPEC=C:\WINDOWS\COMMAND.COM
!C:=C:\cygwin\bin
CMDLINE=bash --login -i
HOSTNAME=CANTEEN
WINDIR=C:\WINDOWS
WINBOOTDIR=C:\WINDOWS
PS1=#
USER=tyler
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;0
1:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;
31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.jar=01;31:*.deb=01;31:*.jpg=01;3
5:*.gif=01;35:*.bmp=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=
01;35:*.ico=01;35:*.mpg=01;37:*.avi=01;37:*.gl=01;37:*.dl=01;37:*.txt=00;33:*.lo
g=00;33:*.html=01;33:*.css=01;33:*.xml=01;33:*.xsl=01;33:*.h=00;32:*.c=00;32:*.c
pp=00;32:*.java=00;32:*.class=01;32:*.pgp=01;30:*.asc=01;30:*.make=00;36:
MACHTYPE=i686-pc-cygwin
OLDPWD=/usr/bin
TEMP=/dosc/WINDOWS/TEMP
TMP=/dosc/WINDOWS/TEMP
SHLVL=1
MAKE_MODE=unix
SHELL=/bin/bash
HOSTTYPE=i686
OSTYPE=cygwin
HOME=/dosc/mydocu~1
TERM=cygwin
PATH=/usr/local/java/bin:/usr/local/bin:/usr/bin:/bin:/dosc/WINDOWS:/dosc/WINDOW
S/COMMAND
_=/usr/bin/printenv
#



>I have also substitutes my .vimrc by the vimrc_example.vim file you're
>referring to.  Nothing happens.
>
>I tried starting vim from tcsh, bash and even cmd but also to no avail.
>
> > >- all vim script files (including .vimrc) must be in binary line
> > >   ending mode.  Convert all CRLF to FL.
> >
> > Given that I just copied the file (/usr/share/vim/vim60/vimrc_example.vim)
> > to my home directory and renamed it to .vimrc, I assume that the line
> > termination is that desired by the program.
>
>Did you actually test it?

Yes, it uses Unix line termination.

I am installing on a Windows 2000 machine to see if I can reproduce the 
problem under that OS. Do you have a Windows 98 box?

Tyler



>Corinna
>
>--
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Developer                                mailto:cygwin AT cygwin DOT com
>Red Hat, Inc.
>
>--
>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/


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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