how to disable the highlighting of parenthesis matching

[Charles Smith]

Hello all,

How can I turn off the highlighting of parenthesis matching?
Grepping in /usr/share/vim/vimcurrent/doc for parenthesis or
match doesn't turn up things that look like likely candidates.

---

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Volker Glave]

On Mar 4, 11:31 am, Charles Smith <cts.priv...@yahoo.com> wrote:
>
> How can I turn off the highlighting of parenthesis matching?

:help matchparen

| To disable the plugin after it was loaded use this command:
| :NoMatchParen

[Robin Wood]

This may be a daft question but how do I specify this (actually I want
the opposite) in my vimrc file? I've tried just DoMatchParen which is
the command which works from the prompt in vim but vim then complains
about an error in the file with it in there.

I also tried set DoMatchParen just in case but as I expected, that didn't work.

Robin

>
> >
>

[Matt Wozniski]

Put this line in your ~/.vimrc:
let loaded_matchparen = 1

NoMatchParen is a command to the loaded plugin to ask it to stop matching.
Setting "loaded_matchparen", on the other hand, stops the plugin from
ever loading (by making it think that it's already running).

~Matt

[Robin Wood]

And what do I set/let it to to make sure that it always loads? 0 doesn't do it.

Robin

[Tony Mechelynck]

Plugins will load by default if they aren't inhibited: you don't need to
do anything.

BTW, there was a buggy version of matchparen.vim recently, which didn't
work in the GUI. The current (fixed) version is dated 2008 Feb 27 on its
third line.

Best regards,
Tony.
--
The reader this message encounters not failing to understand is
cursed.

[Robin Wood]

Matching parens works fine on most of the boxes I use but on one at a
clients site it doesn't work, what I want to do is enable it.

If plugins load by default and I'm not seeing the functionality then I
assume that the plugin isn't installed on the machine which doesn't
surprise me as the version of vim on there was altered in some way so
that it only worked as vi (it was definitely vim, all the version info
said so) till the admins unlocked it.

I'll have a look for the plug in and try to install it, hopefully that
will get things working.

Its weird how something so small can make such a big difference when
editing a file!

Robin

[Tony Mechelynck]

Robin Wood wrote:
> On 05/03/2008, Tony Mechelynck<antoine.m...@gmail.com> wrote:
>> Robin Wood wrote:
>> > On 05/03/2008, Matt Wozniski<m...@drexel.edu> wrote:
>> >> On Tue, Mar 4, 2008 at 6:08 PM, Robin Wood<dni...@gmail.com> wrote:
>> Plugins will load by default if they aren't inhibited: you don't need to
>> do anything.
>>
>> BTW, there was a buggy version of matchparen.vim recently, which didn't
>> work in the GUI. The current (fixed) version is dated 2008 Feb 27 on its
>> third line.
>>
>
> Matching parens works fine on most of the boxes I use but on one at a
> clients site it doesn't work, what I want to do is enable it.
>
> If plugins load by default and I'm not seeing the functionality then I
> assume that the plugin isn't installed on the machine which doesn't
> surprise me as the version of vim on there was altered in some way so
> that it only worked as vi (it was definitely vim, all the version info
> said so) till the admins unlocked it.
>
> I'll have a look for the plug in and try to install it, hopefully that
> will get things working.
>
> Its weird how something so small can make such a big difference when
> editing a file!
>
> Robin

matchparen.vim was introduced with Vim 7, and uses some commands which
were new in that release. Are you sure that that client of yours isn't
still on Vim 6?

"Working as vi" may mean "in compatible mode". Vim starts in
'compatible' mode if it doesn't find a .vimrc or _vimrc, unless there is
-N on the command-line.

Best regards,
Tony.
--
[clop clop]
GUARD #1: Halt! Who goes there?
ARTHUR: It is I, Arthur, son of Uther Pendragon, from the castle of
Camelot. King of the Britons, defeator of the Saxons,
sovereign of
all England!
GUARD #1: Pull the other one!
The Quest for the Holy Grail (Monty
Python)

[Robin Wood]

On 06/03/2008, Tony Mechelynck <antoine.m...@gmail.com> wrote:
>
> matchparen.vim was introduced with Vim 7, and uses some commands which
> were new in that release. Are you sure that that client of yours isn't
> still on Vim 6?
>

That will be it, they are on 6.3.82. That saved me some effort of
trying to get it working.

> "Working as vi" may mean "in compatible mode". Vim starts in
> 'compatible' mode if it doesn't find a .vimrc or _vimrc, unless there is
> -N on the command-line.
>

I don't think it was compatible mode, things like split didn't work
and when talking to the admins they said that they force it into this
other mode deliberately and only they could switch it back.

Robin

[Tony Mechelynck]

Then I suppose it was a "tiny" vim, compiled which most options
disabled. Unabled to split would mean compiled with -windows, which is
indeed typical of a "tiny" build. (Window splitting requires at least a
"small" build, expression evaluation at least a "normal" build,
multi-byte at least a "big" build, etc.: see "help +feature-list" for
details)

To enable window splitting etc., Vim must be recompiled with different
configure options. You could do that yourself, but for it to work you
need not only a C/C++ compiler and linker, but also "development"
packages for all system libraries used by Vim, and if your sysadmins
haven't installed that, or if they have installed them at some place
where you cannot access them, you may have a problem.

Best regards,
Tony.
--
Never drink coke in a moving elevator. The elevator's motion coupled
with the chemicals in coke produce hallucinations. People tend to
change into lizards and attack without warning, and large bats usually
fly in the window. Additionally, you begin to believe that elevators
have windows.

[Robin Wood]

On 06/03/2008, Tony Mechelynck <antoine.m...@gmail.com> wrote:
>
> Then I suppose it was a "tiny" vim, compiled which most options
> disabled. Unabled to split would mean compiled with -windows, which is
> indeed typical of a "tiny" build. (Window splitting requires at least a
> "small" build, expression evaluation at least a "normal" build,
> multi-byte at least a "big" build, etc.: see "help +feature-list" for
> details)
>
> To enable window splitting etc., Vim must be recompiled with different
> configure options. You could do that yourself, but for it to work you
> need not only a C/C++ compiler and linker, but also "development"
> packages for all system libraries used by Vim, and if your sysadmins
> haven't installed that, or if they have installed them at some place
> where you cannot access them, you may have a problem.
>

Thanks for that info, I've no idea why they did a tiny build, it is a
standard server, no restrictions on anything and they were quite happy
to change it to the full build when I asked.

Robin