Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
X-Apparently-From:	<vihs AT rocketmail DOT com>
Message-ID:	<39633F12.359502C8@rocketmail.com>
Date:	Wed, 05 Jul 2000 19:28:42 +0530
From:	Shiv Kumar <vihs AT rocketmail DOT com>
Organization:	Aztec Software, http://www.aztec.soft.net
X-Mailer:	Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: Cygnus + VIM (+ bug in ftp?)
References:	<3962FA0F DOT 2C2032B8 AT rocketmail DOT com>

Hi Corinna/Michael

Thanks for the replies. I believe I took the latest release at the wrong time :-(. I
should have waited for an official mail on cygwin-announce!

For some questions that you have asked, here goes the answer :

>   1. Why do we have these two files, vi.exe and vim.exe in the /bin directory?
>      Is there any difference between the two.

Thanks for clarifying this point.

>   2. If I try to run another VIM script (eg matchit.vim) using :source command
>      inside VIM or in _vimrc file, it complains about trailing ^M characters.
>      But I dont see any ^M chars in that file.

Further diagnosis relvealed the following facts.

   * An 'od -xc' on that file shows \r and \n. Even 'cat -v'  displays ^M, but VIM
     does not .

   * Going by my grandma's trick, I ftp-ed the file to a solaris box in ascii mode
     and got it back in binary mode. I was surprised to see that \r\n were *not*
     changed to \n. I think it may be a bug in Cygwin version of ftp.exe.

   * I tried the same stunt with ftp.exe from \WINNT\system32 directory. This time
     the trick worked. All ^Ms were removed and /bin/vim does not crib anymore about
     trailing characters when :source-d.

>
>   3. Some of my map commands does not work. Eg, :map <C-Q> :q!<CR> does not work
>      when I press CTRL+q. Similarly <C-S> also does not work.

There is no need for my _vimrc file. This is easy to reproduce. Open VIM

     :map <C-Y> :q!<CR>     # this works

Now,

     :map <C-Q> :q!<CR>    # this doesnt work. Neither does <C-S>

>   4. Any file with :syntax on is very hard to read with a black background. The
>      colors were all decent when I used Win32 version of VIM. Where does
>      cygwin-vim pick sytax coloring from?

As one gentleman from vim mailing list suggested, I included the following lines in
my _vimrc file :

     set background=dark
     syntax on

It solved the problem.

Thanks.
--
shiv
vihs AT rocketmail DOT com



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -