X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,TW_YG,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
From:	"Harrington, John" <jharring AT qualcomm DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Tue, 9 Nov 2010 16:14:12 -0800
Subject:	Re: Syntax highlighting not working in vim73
Message-ID:	<0C33B811BB93B3469F549ADBFA84414718BC77B2E8@NALASEXMB08.na.qualcomm.com>
x-cr-hashedpuzzle:	Af7g B1ML DBFw DB1/ DbPO DnrL D1f7 Ek63 Elil Ergb GWCM GhS8 HM6T HdW4 H7z6 IDDF;1;YwB5AGcAdwBpAG4AQABjAHkAZwB3AGkAbgAuAGMAbwBtAA==;Sosha1_v1;7;{BB23F9D6-22D7-486F-B5DE-07384C9AF022};agBoAGEAcgByAGkAbgBnAEAAcQB1AGEAbABjAG8AbQBtAC4AYwBvAG0A;Wed, 10 Nov 2010 00:14:12 GMT;UgBlADoAIABTAHkAbgB0AGEAeAAgAGgAaQBnAGgAbABpAGcAaAB0AGkAbgBnACAAbgBvAHQAIAB3AG8AcgBrAGkAbgBnACAAaQBuACAAdgBpAG0ANwAzAA==
x-cr-puzzleid:	{BB23F9D6-22D7-486F-B5DE-07384C9AF022}
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Thank you very much, Larry.  This worked, though perhaps not for the reason=
 you expected.  Excuse the long description that follows, but the fix raise=
d some issues that I thought I should report.=20=20

I did just as you suggested, removed the C:/utils paths and reinstalled vim.

I then moved all my config files out of the way (including .vimrc and .bash=
rc) and tried :syntax on, which worked.

I then tried moving my .bashrc back to ~ and sourced it.  :syntax on did no=
t work, which told me the problem was a line in my .bashrc.=20

By iteratively cutting the .bashrc in half and sourcing it, I narrowed the =
problem down to this alias, which I have commented out:

     alias vi=3D'vim';

I suspect people will tell me this was never necessary, but I honestly reme=
mber years ago having to put in this alias because when I typed "vi" I got =
an error back that the command was unrecognized, though "vim" was recognize=
d.

I had thought vi was simply an alias.  It is not.  It's a separate utility.

When I type=20

     $ which vi=20

I get:

     /usr/bin/vi

When I type=20

     $ which vim=20

I get:

     /usr/bin/vim

When I type:=20

     $ vim

I get:
                  VIM - Vi IMproved

                     version 7.1
               by Bram Moolenaar et al.
	         [etc.]

When I type:=20

     $ vi

I get:
              VIM - Vi IMproved

                    version 7.3.3
               by Bram Moolenaar et al.
	         [etc.]

7.3.3 is the one I thought I installed.  I don't recall installing a separa=
te utility "vim 7.1", but I guess I must have.  In any case, I'm very satis=
fied that "vi" is now showing syntax.  It puzzles me a bit that the specifi=
c command "vim" still does not work with syntax, but since I never type "vi=
m" (I could easily reverse the above alias, I suppose), I am not concerned.=
=20=20

Thank you again.

Best regards,
John


On 11/9/2010 5:09 PM, Larry Hall wrote:
> On 11/9/2010 4:26 PM, Harrington, John wrote:
> >
> >     Larry Hall, responding to my earlier posting, suggested I post a fo=
llow-up
> >     following the reporting guidelines.
> >
> >
> >     See my root post for the general description.
> >
> >     Larry suggested I move all my configuration files out of the way, o=
pen my
> >     .bashrc and type :syntax on.
> >
> >
> >     I moved my vimrc and .vimrc files to a temp dir from ~ and user/sha=
re/vim and
> >     usr/share/vim73 and opened a new window.  :syntax on still does not=
 work.
> >
> >
> >     I tried moving my .profile and .bashrc files as well.  :syntax on s=
till does
> >     not work.
> >
> >
> >     I enclose my cygcheck log.
>
>
> Thanks. I'd suggest the following:
>
>   1. Remove all paths containing C:/utils from your PATH environment vari=
able.
>   2. Reinstall the 'vim' package via 'setup.exe'.
>   3. Try the test I outlined in my previous email again.
>
>
> --
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 216 Dalton Rd.                          (508) 893-9889 - FAX
> Holliston, MA 01746

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -