Can not get Matchit.vim to work. What am I Doing Wrong?

Janina Sajka janina at
Wed Nov 21 01:15:44 UTC 2007

You're so very right about the ruler. There are other modes that can get
one into trouble--but you have to turn them on.

To my mind the only drawback of vim is that there's no aural way to know
whether you're in edit mode or in command mode. I wish Speakup could
change pitch to indicate that. I'm forever cleaning something up for
making that mistake.


Martin McCormick writes:
> Janina Sajka writes:
> >Honestly, Martin. This doesn't sound like an accessibility issue. Seems
> >you know exactly what is, and isn't happening, and it seems you're able
> >to issue commands to the system. So, unless someone here has direct
> >knowledge of this particular plugin, I don't know why blinux would be
> >the right place to ask your question. Shouldn't you rather rely on the
> >help resources provided via
> 	I actually did begin to wonder if this was an
> accessibility issue, maybe some sort of highlighting that vim
> was doing without moving the cursor. If you move the cursor over
> a left-brace, parenthesis or bracket, you do suddenly hear the
> matching parenthesis or whatever which makes me think vim
> probably highlights where your inclusion ends.
> 	In the overall scheme of things, this is minor, but I
> did sort of wonder what was going on the first time or two.
> 	After about the fifth read of the documentation, I
> realized that that plugin doesn't automatically set up the
> advanced capabilities, only the ability to do them. You have to
> define which clauses to track and put them in your .vimrc file.
> 	There are no screen tricks or anything strange going on
> at all and this makes tracking the flow of a shell script much
> quicker and more accurate.
> I must admit that every time I have thought there was an
> accessibility issue in the command-line world of UNIX, I have
> been wrong. The only thing about vim that may really throw
> someone for a loop at first is if one is on a system in which
> the ruler is set on. You will hear your cursor position in the
> line every time you hit the h or the l. If you put
> set noruler
> in your .vimrc file, then everything is right with the world
> again and the l key echoes the contents of the line one is on,
> just like in vi.
> 	I had this awakening the first time I was on a Redhat
> system which uses vim by default. Many of you use Redhat so you
> probably already know all this, but it was new to me.
> Martin McCormick
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at


Janina Sajka,	Phone:	+1.202.595.7777;	sip:janina at
Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com

Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com

Chair, Open Accessibility	janina at	
Linux Foundation

More information about the Blinux-list mailing list